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/zot/mini-spec/claude-mdgit clone --depth 1 https://github.com/zot/mini-specWhat 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.00488 | $0.00488 |
| Opus 5 | $0.00244 | $0.00244 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
mini-spec 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 2d 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.
What it actually says
Project Guidelines
Releases
Version is tracked in .claude/skills/mini-spec/README.md. Increment the patch number unless the user says otherwise.
Release contents (zip file):
.claude/skills/mini-spec/(skill files).claude/agents/spec-agent.md(agent)- Exclude Emacs backup files:
zip -x "*.~undo-tree~"
Release process:
- Check existing tags (
git tag -l) to confirm next version number - Update version in
.claude/skills/mini-spec/README.md - Commit the skill README (ask user about other new or changed files)
- Tag it (e.g.,
v0.9.3) - Push commit + tag
- Create GitHub release with
gh release create - Upload zip to the release
- Build and upload binaries:
cd tool && make releasethengh release upload <tag> bin/* - Include in release notes:
claude plugin install code-simplifier
Note: Binaries must be rebuilt for each release because they embed the version via --version.
Cursor
If .claude/skills/mini-spec/SKILL.md changes, regenerate .cursor/rules/mini-spec.mdc so Cursor stays aligned:
python tool/gen_cursor_rule.py
Summary specs
The Go tool's specs live in tool/specs/. Summary specs there index per-feature specs along a cross-cutting axis (CLI surface, storage layout, API set, capabilities). Mini-spec's normal anchoring doesn't catch drift in them, so when you add, rename, or retire something along one of these axes, update the matching summary spec by hand.
Summary specs in tool/specs/:
cli-commands.md— full inventory ofminispecsubcommands and global flags. Update whenever a subcommand is added, renamed, or retired.file-formats.md— every file the tool reads or writes, with links to the per-feature spec that defines each format. Update when a file format is added, changed, or retired.
When you create another, list it here so future maintainers know which summary specs to keep in sync.
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.
- 2d ago First seen · 41 lines · 488 tokens per session scan A 172b01527da6
mini-spec CLAUDE.md is an instructions file published in the GitHub repository zot/mini-spec (5 stars, last pushed 2mo ago), licensed MIT. It adds 488 tokens to every session, about $0.0024 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
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
azure-sdk-for-rust changelog.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
stiletto CLAUDE.md
Instructions for benjamin-bader/stiletto, covering stiletto — contributor & agent guide, commit messages: conventional commits (required), breaking changes, examples and how releases work.