mini-spec-spec-agent

A project rule for using the mini-spec method to design, implement, or reconstruct software. It connects architecture documents, code changes, tests, and implementation decisions.

In plain words
What is it for?
Use it for feature design, implementation from a design, updating a design after coding, or reverse-engineering a system with architecture and test artifacts.
Why use it?
It keeps focused architecture work aligned with the project's design records and requires checks when code changes are made without an updated design.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/zot/mini-spec/mini-spec-spec-agent
Clone the repo
git clone --depth 1 https://github.com/zot/mini-spec

Made for: Cursor.

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00025 $0.00222
Opus 5 $0.00013 $0.00111
Sonnet 5 $0.00005 $0.00044
Haiku 4.5 $0.00003 $0.00022

Measured 2d ago against content hash 0c56a6a8f386, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mini-spec-spec-agent 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.

.cursor/rules/mini-spec-spec-agent.mdc · 19 lines

What it actually says

Spec agent (mini-spec)

Use for the same situations as Claude’s spec-agent: designing features, implementing from design, updating design after code, or reverse-engineering with CRC/sequence/test artifacts.

The full methodology lives in mini-spec (always-on project rule). In this chat:

  1. Confirm minispec check-version matches .claude/skills/mini-spec/README.md.
  2. Use todos for phases and per-file work (same intent as Claude tasks).
  3. Design-only when the user asks for design — no code until they approve.
  4. Implementation only with traceability comments and minispec update check / uncheck as required.
  5. On code changes without prior design sync: uncheck artifacts and ask whether to update design, specs, or defer.

MIT License: see .claude/skills/mini-spec/LICENSE.

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. 2d ago First seen · 19 lines · 25 tokens per session scan A 0c56a6a8f386

Subscribe to this mod's changes

mini-spec-spec-agent is a cursor rule published in the GitHub repository zot/mini-spec (5 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 222 once invoked, about $0.0001 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.