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/.skills/execute-pick-spec/SKILL.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/skills/fokkerone/superspecs/execute-pick-spec)<a href="https://agentmods.dev/skills/fokkerone/superspecs/execute-pick-spec"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/execute-pick-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.00054 | $0.01066 |
| Opus 5 | $0.00027 | $0.00533 |
| Sonnet 5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
execute-pick-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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: execute-pick-spec
You are selecting the next spec to execute. This is the gate between planning and execution.
Nothing is dispatched to subagents until this step passes.
Steps
1. List available specs
Scan superspec/specs/. For each directory, read status.md and categorize:
Ready to execute (spec written, not yet started):
- <slug> — <purpose> — context: ~Xk
In progress:
- <slug> — <phase>
Complete:
- <slug>
If the user specified a slug, jump to step 3 with that slug.
If multiple specs are ready, present the list and ask which to pick.
2. Check dependencies
Read the spec's spec.md. Look for the Depends on: field.
For each dependency:
- Is there a spec for it in
superspec/specs/? - Is that spec complete (shipped)?
If unmet dependencies exist:
Cannot execute <slug> yet.
Depends on: <dep-slug> (status: <status>)
Options:
1. Execute <dep-slug> first
2. Remove the dependency if it's not actually needed (update spec)
Do not proceed until dependencies are resolved.
3. Validate the spec
Read spec.md and tasks.md completely. Check:
Completeness
- Every requirement has at least one scenario
- Every scenario is testable (concrete GIVEN/WHEN/THEN)
- tasks.md exists with at least one task
- Done criteria defined
Clarity
- No ambiguous SHALL statements
- No tasks that say "implement X" without specifying the test requirement
- No tasks that depend on unwritten decisions
Context window
- Estimate:
spec.md(~Xk) +tasks.md(~Yk) + typical implementation context (~Zk) - Total must be under 200k
- Report:
Context budget: ~<total>k / 200k
If validation fails, list specific issues and say: "Fix these before execution begins."
4. Create the phase directory
Create superspec/phases/<slug>-execute/:
superspec/phases/<slug>-execute/
├── plan.md ← execution plan (written here)
├── review-log.md ← code review findings (populated during execution)
└── wave-1.md ← populated when Wave 1 starts
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 · 163 lines · 54 tokens per session scan A 3d13f190f329
execute-pick-spec is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,066 once invoked, about $0.0003 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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…