Version, verify, and distribute agent behavior across every repo and tool.
Replace copied CLAUDE.md files, drifting rules folders, and ad-hoc prompt sharing with versioned bundles that install in one command.
Built for platform, DX, and AI-enablement teams standardizing agent behavior.
Why not Git repos or templates?
You could manage agent configs with tools you already have. Here's what you'd give up.
Git submodules
- Versioning
- Git tags (manual)
- Discovery
- Search GitHub
- Cross-tool install
- Manual copy per tool
- Integrity verification
- Git hash (transport-level)
- Team collaboration
- PRs on config repo
Repo templates
- Versioning
- Snapshot at clone time
- Discovery
- Know the repo URL
- Cross-tool install
- Manual copy per tool
- Integrity verification
- None after clone
- Team collaboration
- Fork divergence
Raw OCI
- Versioning
- Tags (manual push)
- Discovery
- Registry UI (if any)
- Cross-tool install
- oras pull + manual wiring
- Integrity verification
- Digest check
- Team collaboration
- No built-in collaboration
Musher
- Versioning
- SemVer with immutable manifests
- Discovery
- Hub catalog + CLI search
- Cross-tool install
- mush bundle load into any harness
- Integrity verification
- SHA-256 per asset, verified on download
- Team collaboration
- Org namespaces, RBAC, visibility controls
How platform teams use Musher
Standardize agent behavior across repos, tools, and teams.
Enforce API governance across every service
Publish OpenAPI linting rules, naming conventions, and breaking-change policies as a single bundle. Every team gets the same standards — updated centrally, installed per-repo.
Pin agent behavior to a known-good version in CI
Lock review rules and security checklists to a SemVer release in your pipeline. When a bundle update breaks something, roll back in one line — no config drift, no mystery regressions.
Distribute domain expertise as installable packages
Package compliance rules, infrastructure playbooks, and onboarding guides so every repo and agent surface gets production-ready behavior from day one.
CLI or SDK
CLI for installing bundles. SDKs for programmatic access.
Mush CLI
Install bundles into any project directory. The CLI writes assets where agent harnesses (Claude Code, Codex, OpenCode) pick them up automatically.
Local dev, CI pipelines, any agent harness
$ mush bundle load musher/code-review TypeScript & Python SDKs
Pull bundle metadata and assets programmatically for CI policy gates, application code, or custom tooling.
App code, custom tooling, CI policy gates
$ npm install @musher-dev/musher-sdk $ pip install musher-sdk Featured bundles from the Hub
Real governance packs you can install today.
musher/openapi-specification-governance OpenAPI Specification Governance
Enforce naming conventions, versioning rules, and breaking-change policies across your API specs.
$ mush bundle load musher/openapi-specification-governance musher/database-schema-governance Database Schema Governance
Standardize migration patterns, naming conventions, and index policies for your database schemas.
$ mush bundle load musher/database-schema-governance musher/developer-docs-authoring Developer Docs Authoring
Style guides, structure templates, and review rules for technical documentation.
$ mush bundle load musher/developer-docs-authoring Built for trust at every layer
Open source, immutable versions, and cryptographic verification — not just promises.
Open source
Inspect every line. MIT-licensed CLI and SDKs.
Immutable versions
Published bundles are append-only. No silent overwrites.
SHA-256 verification
Every asset is hash-verified on download.
OCI-compatible
Built on OCI artifact standards. No vendor lock-in.
Org RBAC
Namespace bundles to your org. Control who publishes.
Audit & provenance
Track who published what, when, and which version.
Built by the engineer behind RunPod's Python SDK (5.2M+ downloads).
Start distributing agent behavior today.
Free to use. One command to install any public bundle.
$ curl -fsSL https://mush.musher.dev | sh