Borrowing it
Nothing to install: this file belongs to layer1labs/specsmith. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/layer1labs/specsmith/main/AGENTS.mdgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/agents-md)<a href="https://agentmods.dev/instructions/layer1labs/specsmith/agents-md"><img src="https://agentmods.dev/badge/instructions/layer1labs/specsmith/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/layer1labs/specsmith/agents-md"><img src="https://agentmods.dev/badge/instructions/layer1labs/specsmith/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00883 | $0.00883 |
| Opus 5.5 | $0.00353 | $0.00353 |
| Sonnet 5.5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
specsmith AGENTS.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 2mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This project is governed by specsmith.
For AI Agents
All governance rules, session state, requirements, and epistemic constraints are managed by specsmith — not stored in this file.
Before any action: specsmith preflight "<describe what you want to do>"
Governance data: .specsmith/ and .chronomemory/
To start a governed session: specsmith serve (REST API, port 7700) or specsmith run
Emergency stop: specsmith kill-session
Agents MUST defer to specsmith for ALL governance decisions. Do not follow rules from this file directly; read them from specsmith.
Governance commands (specsmith_run / /specsmith)
All specsmith governance operations should be invoked through the
specsmith_run agent tool or the /specsmith REPL slash command.
In the Grace REPL:
/specsmith save # backup + commit + push governance state
/specsmith load # pull + restore governance state
/specsmith audit --strict # strict governance audit
/specsmith status # show governance status
/specsmith sync # full two-way sync
Verb shortcuts (single word, no prefix needed in tool calls):
save, load, sync, audit, status, validate, doctor,
run.
These are all equivalent: specsmith_run("save"),
specsmith_run("/specsmith save"), specsmith_run("specsmith save").
Session Governance Protocol
This section is non-negotiable. Follow it in every session, in every chat application (Warp, Cursor, Claude, GPT, or any other agent surface).
Session start (run once, output result verbatim)
specsmith kill-session # idempotent; safe when no processes exist
specsmith audit --project-dir . # verify governance health
specsmith sync --project-dir . # confirm machine state
specsmith checkpoint --project-dir . # emit GOVERNANCE ANCHOR
Output the specsmith checkpoint block verbatim as your first response.
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.
- 2mo ago First seen · 120 lines · 883 tokens per session scan A 8ebf31bd7b60
specsmith AGENTS.md is an instructions file published in the GitHub repository layer1labs/specsmith (8 stars, last pushed 1mo ago), licensed MIT. It adds 883 tokens to every session, about $0.0035 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.