Every team building on agents ends up rebuilding the same thing: durable state, a deterministic loop, fresh workers, independent verification, signed proof — always similar, always a little different, never a standard. The Frontier SDK is the installable plumbing for that harness — protocols, reducers, conformance tools, and adapters — so you assemble a governed deployment instead of redefining the standards, and build your application, not another bespoke agent loop.
SDK
The implementation family for the Frontier standards: install the pieces of a governed agent harness instead of rebuilding them from scratch. Versioned code owns protocol and scoring semantics so results stay comparable across model and host updates.
Core components on npm · MIT · public source
npm install @frontier-infra/protocolnpx -y @frontier-infra/audit run . --out ../frontier-audit-outnpm install @frontier-infra/avlEach piece is independently useful; together they cover the whole journey — declare ground truth, keep workers honest, run the loop, watch its health, audit conformance, and sign the proof. Install what your deployment needs.
Runtime health
Types and a deterministic, fail-closed reducer for the four-layer runtime health record (process / scheduler / execution / governance) a Machine deployment emits. Python binding and golden cross-language fixtures live in the SDK repo.
npm install @frontier-infra/protocol
View →Conformance audit
Score a repository against The Machine's static conformance kit, bind the verdict to Git state, and optionally issue a signed AAR receipt. The evidence packet records the exact CLI version that produced it.
npx -y @frontier-infra/audit run <repo> --out <dir>
View →Ground truth
Make your application agent-readable so verifiers check declared state — not a worker's narrative and not a scraped guess.
npm install @frontier-infra/avl
View →Signed receipts
Ed25519-signed Agent Attestation Records: portable proof of claim vs. independently verified verdict. The spine every other layer emits.
zero-dep signer/verifier in the AAR repo · npm package on the roadmap
View →Reference harness
Working deployments of The Machine to start from — a deterministic code-work driver and an orchestrator-shaped ops template — instead of a blank page.
clone and adapt
View →Worker discipline
Contract-and-proof discipline for the coding agents doing the work, with machine-level enforcement for Claude Code.
install.sh into the coding harness
View →Plugins teach a host to use the stack — they never own protocol or scoring semantics. Both run the same published CLI, so a host update can change how the workflow is invoked without silently changing what a score means.
Claude Code
A ten-skill field kit for designing governed harnesses, plus an audit skill that runs the published @frontier-infra/audit CLI via npx — no bundled scoring rules in prompts, no bootstrap machinery.
Live · /plugin marketplace add frontier-infra/plugins
View the marketplace repo →Codex
Runs the same published CLI via npx. The evidence packet's recorded version is the pin; host permission systems own install trust.
Thin adapter · public source
View Codex adapter source →Packages are added only when they have an executable vertical slice — never as architecture placeholders. Next slices: the AAR signer/verifier as an npm package, the Python protocol binding on PyPI, and a contract schema for Box-0 goal contracts.
Questions, release issues, or sensitive reports? Start at Support. The local execution and data boundaries are documented in Privacy and Terms.