Borrowing it
Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/AGENTS.mdgit 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/instructions/fokkerone/superspecs/agents-md)<a href="https://agentmods.dev/instructions/fokkerone/superspecs/agents-md"><img src="https://agentmods.dev/badge/instructions/fokkerone/superspecs/agents-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.
<a href="https://agentmods.dev/instructions/fokkerone/superspecs/agents-md"><img src="https://agentmods.dev/badge/instructions/fokkerone/superspecs/agents-md.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.00846 | $0.00846 |
| Opus 5.5 | $0.00338 | $0.00338 |
| Sonnet 5.5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
superspecs AGENTS.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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperSpecs — Agent Bootstrap
SuperSpecs: spec-driven planning + parallel TDD execution + wiki memory.
Commands
Claude Code / Cursor: /superspecs:<cmd>
OpenCode: /superspecs-<cmd>
Lifecycle (always in order)
Phase 0 — Setup
/superspecs:techstack— questionnaire: define stack, get skill & library recommendations, save to wiki
Phase 1 — Plan
/superspecs:design-import <path>— (optional) import DesignOS export → design-context.md; enriches /discuss + /spec with design constraints, data shapes, milestone structure, and test scaffolding/superspecs:discuss— capture decisions before planning; required before /spec/superspecs:spec— write spec (fits 200k context window); requires DISCUSS.md/superspecs:grill— mandatory gate: stress-test spec against wiki + techstack; READY verdict required before /pick-spec; requires spec.md
Phase 2 — Execute
/superspecs:pick-spec— validate spec, check context fit/superspecs:branch— create branch/worktree/superspecs:subagent— fresh subagent per task; RED→GREEN→REFACTOR TDD runs inside each task/superspecs:tdd— invoke directly if writing code outside of subagent mode/superspecs:code-review— critical issues block progress
Phase 3 — Verify
/superspecs:verify— full suite + scenario coverage (Stage 1), then compile feature to wiki (Stage 2); gate between stages blocks wiki import if tests fail
Phase 4 — Ship
/superspecs:ship— PR, archive, next cycle
Wiki Operations (run any time)
/superspecs:wiki-query— tiered retrieval query; answer stays in context or files back as a page/superspecs:wiki-lint— health check: orphans, broken links, contradictions, stale refs/superspecs:cross-linker— auto-insert[[wikilinks]]for unlinked mentions/superspecs:wiki-status— vault dashboard: size, hubs, tags, provenance, pending sources/superspecs:wiki-capture— save session findings to wiki (--quickor--full)/superspecs:tag-taxonomy— canonical tag vocabulary; audit and normalize vault-wide/superspecs:wiki-rebuild— archive + rebuild vault; restore from snapshot
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.
- 1mo ago First seen · 67 lines · 846 tokens per session scan A 20edebd995f4
superspecs AGENTS.md is an instructions file published in the GitHub repository fokkerone/superspecs (5 stars, last pushed 1mo ago), licensed MIT. It adds 846 tokens to every session, about $0.0034 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 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).
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.
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).
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.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.