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 skills/fokkerone/superspecs/plan-specnpx skills add fokkerone/superspecs --skill plan-specgit 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/skills/fokkerone/superspecs/plan-spec)<a href="https://agentmods.dev/skills/fokkerone/superspecs/plan-spec"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/plan-spec.svg" alt="Measured on agentmods" 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.00048 | $0.01723 |
| Opus 5 | $0.00024 | $0.00861 |
| Sonnet 5 | $0.00010 | $0.00345 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
plan-spec 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 6d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: plan-spec
You are writing the feature spec. This is the contract between planning and execution.
Prerequisite: superspec/specs/<slug>/DISCUSS.md must exist. If it doesn't, stop and say: "Run /discuss first to capture decisions before writing the spec."
What a spec is
A spec is a precise description of system behavior — not implementation details. It answers: what must the system do? Not: how does it do it?
It uses SHALL for requirements. It uses GIVEN/WHEN/THEN for scenarios. Every requirement is testable.
The 200k Context Window Constraint
The complete spec — plus the implementation context — must fit in a fresh 200k-token context window. This is not optional. It's what makes parallel execution possible: each executor starts clean.
Target: spec.md under ~3,000 words. If you find yourself writing more, the feature is too large. Decompose it.
Steps
1. Read DISCUSS.md and design-context.md
Read superspec/specs/<slug>/DISCUSS.md. Do not proceed without understanding it fully.
Then check for superspec/specs/<slug>/design-context.md. If it exists, read it completely before writing the spec. It carries design constraints from a DesignOS export — treat them as fixed inputs, not decisions to re-make:
- Design system constraints → add to Non-Functional Requirements + Out of Scope
- Data contract types → add an Interface/Contract section or enrich Requirements
- Milestone structure → use as the wave structure in
tasks.md - Test scaffolding → use as starting points for GIVEN/WHEN/THEN scenarios (adapt, don't copy verbatim)
- Open questions → check if they were answered in
DISCUSS.md; if not, surface them in the spec's Out of Scope or flag them
DISCUSS.md carries the human decisions. design-context.md carries the design constraints. The spec merges both.
2. Query the wiki for relevant patterns
Perform a tiered wiki scan for patterns, interfaces, and decisions relevant to this feature:
Tier 1 — Index scan:
- Read
superspec/wiki/Home.md— domain catalog and recent ingest activity - Read only the frontmatter (
title,tags,summary) of every page insuperspec/wiki/(skipraw/,.obsidian/) - Score for relevance to this feature's domain
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.
- 6d ago First seen · 222 lines · 48 tokens per session scan A aa7bf7f0688e
plan-spec is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,723 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…