mini-spec: Instructions file for Claude Code

CLAUDE.md

mini-spec CLAUDE.md is an instructions file for Claude Code from zot/mini-spec. It costs 1,056 tokens per session, scanned A, original, MIT.

Project instructions for a mini-spec tool, including guidance on releases, version numbers, Cursor rules, and summary specifications. They describe the files and steps used when preparing a release.

In plain words
What is it for?
Use them when updating the mini-spec skill, regenerating its Cursor rule, checking the next version, packaging files, building binaries, or preparing a GitHub release.
Why use it?
They keep release files, version updates, generated editor instructions, and package contents consistent. This reduces the chance of publishing an incomplete or mismatched release.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths.

This is zot/mini-spec's own configuration. It tells Claude Code how to work on mini-spec itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mini-spec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zot/mini-spec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zot/mini-spec/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/zot/mini-spec

Made for: Claude Code.

Wrote 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.

agentmods badge for mini-spec CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zot/mini-spec/claude-md/github.svg)](https://agentmods.dev/instructions/zot/mini-spec/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/zot/mini-spec/claude-md"><img src="https://agentmods.dev/badge/instructions/zot/mini-spec/claude-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.

agentmods 80×15 button for mini-spec CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zot/mini-spec/claude-md"><img src="https://agentmods.dev/badge/instructions/zot/mini-spec/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,056 This file is loaded in full into every session.
When invoked 1,056 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01056 $0.01056
Opus 5.5 $0.00422 $0.00422
Sonnet 5.5 $0.00211 $0.00211
Haiku 4.5 $0.00106 $0.00106

Measured 5d ago against content hash abaf23f5ada0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 5d 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.

CLAUDE.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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/skills/minimap/ (skill files) — required, not optional: SKILL.md's first instruction is to invoke /minimap, so a zip without it ships a skill whose opening directive points at nothing. v2.9.0 ships exactly that broken pair: minimap was split out in 520a783 (2026-06-07), the tag landed 2026-06-09, and the zip's SKILL.md names /minimap three times with no minimap alongside it.
  • .claude/agents/{spec-agent,alarm-puller,measurer,coder}.md (agents) — all four: SKILL.md tells agents to spawn alarm-puller and measurer, so leaving them out ships the same dangling directive as the minimap case below. Name them rather than zipping the directory: code-simplifier.md there is untracked and comes from the plugin. Through v2.11.0 the list named only spec-agent; v3.0.0 is the first zip with all four.
  • Exclude Emacs backup files: zip -x "*.~undo-tree~"
  • Exclude .claude/skills/mini-spec/notes.md: it is git-ignored private notes, and zip -r takes the whole directory, tracked or not. The v4.0.1 build picked it up until the file list was compared with v4.0.0's zip. Compare the new zip's file list with the previous release's before uploading: diff <(unzip -Z1 new.zip | sort) <(unzip -Z1 old.zip | sort).

Release process:

  1. Check existing tags (git tag -l) to confirm next version number
  2. Update version in .claude/skills/mini-spec/README.md
  3. Commit the skill README (ask user about other new or changed files)
  4. Tag it (e.g., v0.9.3)
  5. Push commit + tag
  6. Create GitHub release with gh release create
  7. Upload zip to the release
  8. Build and upload binaries: cd tool && make release then gh release upload <tag> bin/minispec-* (release also rebuilds the host's bin/minispec, which is not a release asset)
  9. Include in release notes: claude plugin install code-simplifier

Read the full file on GitHub · 70 lines

Changes

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.

  1. 5d ago Changed · +1 lines · +26 tokens per session abaf23f5ada0
  2. 21d ago Changed · +4 lines · +113 tokens per session 9ee7c55b1737
  3. 1mo ago Changed · +24 lines · +429 tokens per session 3c915facf465
  4. 2mo ago First seen · 41 lines · 488 tokens per session scan A 172b01527da6

Subscribe to this mod's changes

mini-spec CLAUDE.md is an instructions file published in the GitHub repository zot/mini-spec (5 stars, last pushed 5d ago), licensed MIT. It adds 1,056 tokens to every session, about $0.0042 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

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.

denoland/deno · 3,077 tokens