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/fokkerone/superspecsWrote 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/fokkerone/superspecs/superspecs)<a href="https://agentmods.dev/rules/fokkerone/superspecs/superspecs"><img src="https://agentmods.dev/badge/rules/fokkerone/superspecs/superspecs/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/fokkerone/superspecs/superspecs"><img src="https://agentmods.dev/badge/rules/fokkerone/superspecs/superspecs.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.00307 | $0.00307 |
| Opus 5.5 | $0.00123 | $0.00123 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
superspecs 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.
What it actually says
SuperSpecs Active
Four phases, always in order: Plan → Execute → Verify → Ship
Commands
| Phase | Command | What |
|---|---|---|
| 1.1 Plan | /discuss |
Capture decisions before planning |
| 1.2 Plan | /spec |
Write spec (requires DISCUSS.md) |
| 1.3 Plan | /grill |
Mandatory gate — READY verdict required before execution |
| 2.1 Execute | /pick-spec |
Validate + prepare execution |
| 2.2 Execute | /branch |
Create branch/worktree |
| 2.3 Execute | /subagent |
Parallel task dispatch |
| 2.4 Execute | /tdd |
RED-GREEN-REFACTOR |
| 2.5 Execute | /code-review |
Between tasks, critical blocks |
| 3 Verify | /verify |
Full suite + scenario coverage, then wiki import |
| 4 Ship | /ship |
PR + archive + next cycle |
Hard Rules
- No implementation code before a failing test
- Critical code-review findings block all progress
- Spec must fit a fresh 200k context window
/grillmust reach READY verdict before/pick-spec- Every shipped feature gets a wiki page
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 · 32 lines · 307 tokens per session scan A c9d1e6f7ff5b
superspecs is a cursor rule published in the GitHub repository fokkerone/superspecs (5 stars, last pushed 1mo ago), licensed MIT. It adds 307 tokens to every session, about $0.0012 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 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.