Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/supernova-labs/agent-smith/claude-mdgit clone --depth 1 https://github.com/supernova-labs/agent-smithWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/supernova-labs/agent-smith/claude-md)<a href="https://agentmods.dev/instructions/supernova-labs/agent-smith/claude-md"><img src="https://agentmods.dev/badge/instructions/supernova-labs/agent-smith/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00462 | $0.00462 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
agent-smith CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Smith — Development Guide
This repository distributes the same Agent Smith skill to Claude Code, Codex, and Cursor.
Invariants
agent-smith/skills/agent-smith/is the single canonical skill source.- Root marketplace manifests for Claude, Codex, and Cursor all resolve to
agent-smith/. - Native plugin manifests live under
agent-smith/and consume the same skill tree. - All plugin manifests must agree on
nameandversion. agent-smith/skills/agent-smith/SKILL.mdmust use portable frontmatter and stay below 500 lines.- Harness-specific formats belong in references, templates, or manifests rather than the shared workflow.
.agent-smith/index.jsonuses schema 2.0 and must cover every component/target pair.- Validation must report unavailable runtime smoke tests as
not run, not passed.
Important paths
.claude-plugin/marketplace.json— Claude marketplace catalog.agents/plugins/marketplace.json— Codex marketplace catalog.cursor-plugin/marketplace.json— Cursor marketplace catalogagent-smith/— installable plugin package shared by all catalogsagent-smith/skills/agent-smith/SKILL.md— portable workflowagent-smith/skills/agent-smith/references/— architecture and harness referencesagent-smith/skills/agent-smith/scripts/— deterministic inspection, migration, and validationagent-smith/skills/agent-smith/references/templates/— portable and harness-specific templatestests/— isolated repository fixtures and regression tests
Validation
bash agent-smith/skills/agent-smith/scripts/validate.sh
python3 -m unittest discover -s tests -v
For runtime verification, load or install the repository separately in Claude Code, Codex, and Cursor. Authentication-dependent checks are release requirements but must remain distinct from structural validation.
Releases
- Keep all three plugin manifest versions synchronized.
- Update
CHANGELOG.mdfor every release. - Validate the repository before tagging.
- Record structural and runtime results for all targets.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 43 lines · 462 tokens per session scan A a1a6c9f3d522
agent-smith CLAUDE.md is an instructions file published in the GitHub repository supernova-labs/agent-smith (9 stars, last pushed 1mo ago), licensed MIT. It adds 462 tokens to every session, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.