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.
git clone --depth 1 https://github.com/zot/mini-specWrote 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/rules/zot/mini-spec/minimap)<a href="https://agentmods.dev/rules/zot/mini-spec/minimap"><img src="https://agentmods.dev/badge/rules/zot/mini-spec/minimap/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/rules/zot/mini-spec/minimap"><img src="https://agentmods.dev/badge/rules/zot/mini-spec/minimap.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.01815 | $0.01815 |
| Opus 5.5 | $0.00726 | $0.00726 |
| Sonnet 5.5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
minimap 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 26d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minimap
How a mini-spec project is laid out, so you can find your way around it —
read it, search it, follow a clue from any layer to the others. This is the
model, not the process. The mini-spec rule carries the process and
builds on this one; both apply at all times.
Design docs first — not code
When understanding a feature or planning a change, start with
design/design.md and the relevant CRC cards/sequences before using
code-exploration tools (grep, symbol search, reading source). Design docs are
the project index — they show component relationships, responsibilities, and
code-file mappings more efficiently than reading code. Drop into code-level
tools only after the design docs have oriented you. And when the project keeps
a root spec index (below), read that first of all — it maps every spec
in one file, so you orient without grepping the specs/ tree.
The three levels
specs/ # Human intent — current state, in the user's own words
migrations/ # In-flight migrations — temporary, moved on completion
complete/ # Completed migrations, numbered in landing order
design/ # AI translation — requirements.md, crc-*, seq-*, ui-*, test-*, manifest-ui.md
docs/ # user-manual.md, developer-guide.md
src/ # Code with traceability comments
(src/ stands in for the project's code root, whatever it's named.)
Specs are the human's voice — what the system should do, in natural language, organized by feature area. Intent, not implementation. For libraries, API signatures live in specs because they are the contract. Most specs are per-feature (one spec, one capability). A second kind, summary specs, indexes existing behavior along a cross-cutting axis without adding behavior of its own (below).
Design is the AI's translation of specs into buildable structure.
requirements.md extracts testable statements; CRC cards assign
responsibilities to components; sequences show how components interact.
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.
- 26d ago Changed · +10 lines · +191 tokens per session 353def5ef991
- 1mo ago First seen · 133 lines · 1,624 tokens per session scan A 689f75d2a923
minimap is a cursor rule published in the GitHub repository zot/mini-spec (5 stars, last pushed 5d ago), licensed MIT. It adds 1,815 tokens to every session, about $0.0073 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-09-25.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).