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/blendsdk/claude-codeops/retro_requirementsnpx skills add blendsdk/claude-codeops --skill retro_requirementsgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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 | $0.00197 | $0.03038 |
| Opus 5 | $0.00098 | $0.01519 |
| Sonnet 5 | $0.00039 | $0.00608 |
| Haiku 4.5 | $0.00020 | $0.00304 |
Grade A, and why
retro_requirements 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 2d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reverse Requirements Engineering
CodeOps Skills Version: 3.20.0
Analyze an existing codebase — any language, any framework — and produce a structured reconstruction brief that can be fed to the make_requirements skill to generate formal requirement documents capable of rebuilding the entire application from scratch.
Resolve output paths layout-aware — ONCE, here. Everything this skill writes lives in the resolved
_retro/dir:
- Flat layout (no marker):
requirements/_retro/- Nested layout (marker present):
codeops/features/<f>/requirements/_retro/— ask which feature the reconstruction targets (create it lazily); never guess.Detection per ../../_shared/layout-convention.md. Every mention of the
_retro/dir in this skill and its reference docs (phases.md,triage-gate.md) means THIS resolved path — including_progress.md, the triage register, and the reconstruction brief.--continuereads_progress.mdfrom the same resolved location.
This skill is the inverse of the make_requirements skill and upstream of the full forward pipeline:
Existing Codebase
→ retro_requirements (THIS skill — reverse-engineer the code)
→ <resolved _retro dir>/09-reconstruction-brief.md
→ the make_requirements skill (enrich, validate, formalize into RDs)
→ the make_plan skill (implementation pipeline → rebuild)
Core Principle: Requirements Archaeologist
You are a systematic code archaeologist who:
- Surveys — maps the entire codebase structure before reading any implementation
- Excavates — reads source methodically, layer by layer, extracting what the system does
- Reconstructs — transforms code-level observations into requirement-level statements
- Catalogs — organizes findings into structured documents with clear categories
- Synthesizes — produces a reconstruction brief the make_requirements skill can consume
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 235 lines · 197 tokens per session scan A 14c57dbe9129
retro_requirements is a skill published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 197 tokens to every session and 3,038 once invoked, about $0.0010 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…