Hash-verified installs
Each file is checked against the lockfile before it’s written. facet verify detects drift after installation.
The team standard for AI coding agents
Different agents.
One team standard.
Give every developer’s AI assistant the same approved skills and tools, kept in sync automatically.
Pilot openTeam tier free for 6 months for design partners →HOW IT WORKS
STEP 01 / 03·Package once
- ✎Review instructionsSkill
- ◎Reviewer assistantAgent
- /“/review” shortcutCommand
- ⇄Internal docs connectionMCP server
◇
TEAM STANDARD
Code review playbook
4 items
v2.1Sealed & verified ✓
CHANGE REQUESTWaiting for reviewApproved ✓
Update Code review playbook
v2.0 → v2.1
- +Flag pull requests without tests
- ~Clearer security guidance
- −Remove outdated style rule
PTPlatform team✓SESecurity✓
ALWAYS ON RECORD
Who changed what, who approved it, and when. Every update is reviewed before it reaches anyone’s assistant.
◇v2.1Approved
- MMayaClaude Codev1.4 · outdatedv2.1 ✓
- SSamCodexEdited locallyv2.1 ✓
- PPriyaOpenCodeNot installedv2.1 ✓
- CICI pipelineEvery buildv1.9 · outdatedv2.1 ✓
0 of 4 in sync4 of 4 in sync
WORKS WITH THE AGENTS YOUR TEAM ALREADY RUNSClaude CodeOpenCodeCodex+ any agent via the Adapter SDK ↗
Why teams adopt
One place to manage
what your agents run.
Today, shared agent configuration lives in copied folders, per-tool directories, and chat threads. It drifts quietly until something breaks.
WITHOUTThe same skill is copied into every tool and repository, and the copies diverge without anyone noticing.
WITH AGENT FACETSOne package. Adapters write each tool’s native layout from the same source.
WITHOUTAgent instructions and MCP server declarations get edited in place, with no version, no diff, and no owner.
WITH AGENT FACETSUpdates arrive as a manifest and lockfile diff, approved in your normal pull request flow.
WITHOUTNew hires and CI start from whatever was copied last. Nobody can say exactly what an agent was running.
WITH AGENT FACETS
facet install restores the exact locked configuration and verifies every file by hash.EXAMPLE PACKAGE AND OUTPUT
See it in action
From missing command
to verified install.
One command finds a facet in the public registry, verifies every file by hash, and installs it for each coding tool your team uses.
Install the facet CLIRead the install script ↗
$curl -fsSL https://agentfacets.io/install | bashPublic facets are free to download and publish, always. Sign up to publish →
Open beta · MIT-licensed CLI and open specification
ILLUSTRATIVE SESSION · PUBLIC REGISTRY FACET
The engineering underneath
Agent capabilities.
Managed as dependencies.
The same building blocks your team already trusts for code: manifests, lockfiles, hashes, and review.
Portable installations
One locked facet works across every supported coding tool. Adapters are open source and straightforward to write, so you don’t wait for vendor support.
Write your own adapter with the SDK →Multiple primitives
SkillsCommandsAgentsMCP servers
Multiple adapters
Reproducible environments
Exact versions, pinned by hash. The manifest records intent and the lockfile records resolution, and both are version-controlled. Every environment resolves identically.
Read the open specification →facets.json"@agentfacets/address-pr-feedback": "2.*"facets.lock"version": "2.0.5"
"integrity": "sha256:4086e779…d70bd3"
"integrity": "sha256:4086e779…d70bd3"
Verified assets
Every file is hashed and verified before anything is written to disk, so what was published is exactly what you install. facet verify confirms installed state matches the lockfile at any time.
SKILLskills/address-pr-feedback-rules/SKILL.mdsha256:28f2b981…1c3980✓AGENTagents/address-pr-feedback.mdsha256:8d13a628…2b4c03✓COMMANDcommands/address-pr-feedback.mdsha256:1bc6f009…cce203✓
Composable capabilities In development
Facets that build on facets. Compose a front-end facet from the TypeScript and React facets you already trust, with one resolved graph and one lockfile.
See the roadmap →frontend-ts-reacttypescript-proreact-gurufrontend-patterns
Security & trust
Verify what’s installed.
Review what changes.
A facet puts text into an agent’s context and can declare servers that run commands. That’s why content verification and execution consent are part of the core specification, not optional hardening.
Changes through code review
Manifest and lockfile live in your repository. A new version or a new MCP server shows up as a diff your reviewers approve.
Declared MCP servers
MCP servers are declared explicitly in the facet manifest, so you can see what a package wants to run before you install it.
Open and auditable
MIT-licensed CLI, an open specification, and an install script you can read before running it. No black box between you and your agents.
Private facets
Private facets are visible only inside your organization’s account. They are never published publicly or shared with other customers.
Install-time approval
Security and platform admins pre-approve which MCP servers are allowed to run. Pilot partners are shaping this workflow now.
Running a security review?
We’ll walk your security and platform teams through the integrity model, install behavior, and MCP server handling, and map them against your requirements.
Who it’s for
Built for the people
behind the rollout.
Start with the team that maintains developer tooling. Give engineering leaders and security a concrete configuration to evaluate.
Scope a pilot ↗Platform & DevEx
Maintain shared capabilities across tools and repositories from one source. Retire the hand-maintained sync scripts, symlinks, and copy steps.
Engineering leaders
Roll out agent configuration the way you roll out any dependency: versioned, reviewed, and reproducible, with a bounded pilot before you expand.
Security teams
Review package contents, sources, and MCP server declarations before they reach a developer machine. See the trust model →
Pricing
Free in the open.
Private when you need it.
The CLI, specification, and public registry stay free. Teams pay for private distribution and organization controls.
Public
Freealways
For individual developers and open-source publishers.
- Download and publish public facets
- MIT-licensed CLI and open specification
- Claude Code, OpenCode, and Codex adapters
- Open-source Adapter SDK
Team Pilot open
$10/ seat / month
For engineering teams standardizing agent configuration.
- Everything in Public
- Private facets, visible only to your organization
- Organization management and access controls
- Direct line to the founding team during the pilot
Pilot partners get the Team tier free for 6 months.
Enterprise
Let’s talk
For organizations with security, procurement, and rollout requirements.
- Everything in Team
- Security review walkthrough
- Rollout planning across teams
- Install-time approval for MCP servers In development
Before your team adopts
Straight answers.
Does Agent Facets replace our coding tools?
No. Developers keep the coding agents they already use. Agent Facets packages and installs capabilities for them, and adapters handle each tool’s native layout.
Can we keep our facets private?
Yes. On the Team tier, private facets are visible only inside your organization’s account. Nothing you publish privately is exposed publicly or shared with other customers.
Which coding tools are supported?
Claude Code, OpenCode, and Codex today. The open-source Adapter SDK lets you add any other harness without waiting for us.
What exactly is reproducible?
The configuration: every packaged asset and resolved version, pinned by hash in facets.lock. Model output still varies with the model and runtime, but with an identical configuration, differences come from the model and not from configuration drift.
How do MCP servers fit our security review?
MCP servers are declared in the facet manifest and arrive in your repository as reviewable changes. An install-time approval workflow, where admins pre-approve what may run, is in active development. If your organization needs it before a wider rollout, tell us during the pilot. See the trust model →
What does a pilot involve?
A 30–45 minute kickoff call where we install together, live, in your real repository. Then 2–6 weeks of everyday use with day-3 and day-14 check-ins and a direct line to the founding team. The Team tier is free for 6 months, and there’s no obligation at the end.
Can we uninstall or roll back?
Yes. The lockfile records exactly what was installed, so removal is clean and rolling back is a normal revert.
Design partner pilot
One team.
One shared workflow.
Installed live on the call.
Bring one piece of configuration you already maintain by hand: a shared prompt, a house style guide, an internal MCP connection. We package it with you and install it in your real repository on the kickoff call.
01 / KICKOFF30–45 min · live install in your repo
02 / ACTIVE USE2–6 weeks · direct line to the team
03 / CHECK-INSDay 3 + Day 14
04 / DECIDEExpand based on evidence
6 months Team tier freeNo obligationClaude Code · OpenCode · Codex
Prefer to explore on your own? Read the documentation ↗
Built in the open
SourceGitHub ↗
MIT-licensed CLI, adapters, and Adapter SDK.
StandardSpecification ↗The open facet format, lockfile, and integrity model.
ReferenceCLI reference ↗Every command, flag, and output.
MomentumChangelog ↗What shipped, release by release.
DirectionRoadmap ↗What’s next, including composition and install-time approval.