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/context4ai/workflow/reviewnpx skills add context4ai/workflow --skill reviewgit clone --depth 1 https://github.com/context4ai/workflowWhat 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.00046 | $0.03370 |
| Opus 5 | $0.00023 | $0.01685 |
| Sonnet 5 | $0.00009 | $0.00674 |
| Haiku 4.5 | $0.00005 | $0.00337 |
Grade A, and why
review 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review - PRD and Plan Consistency Review
Review the consistency between the PRD (Product-layer graph) and the Plan (Code-layer graph), identifying blocking issues.
Design Workspace (design-dir)
The default workspace for design documents is design/. On startup the Agent checks:
design/directory exists --> usedesign/as<design-dir>design/does not exist --> pause and ask the user for the design workspace path, explaining the accepted directory structure:<design-dir>/<version>/(prd|plan).md Examples: design/v1.0.1/prd.md, design/v0.5.0/plan.md
design/archive/: Archived or inactive design documents. When exploring existing graph structures, treat as low-priority reference -- read active version directories first and fall back to archive only when relevant context cannot be found in active versions.
All paths below use <design-dir> to refer to this directory.
TL;DR -- Hard Rules
- Spec end-to-end acceptance: Every PRD
[Sn]spec MUST be verifiable through a product interface already available in this version (Web UI preferred, CLI as fallback). "Can be verified once a future version ships" does not count. Specs that can only be verified through API calls, reading code, or running tests are NOT product specs and MUST be reported as a blocking issue - Core: Every PRD
[Sn]spec must be implemented by some Plan[Pn]spec - Traceability matrix: Output a
PRD[Sn] -> Plan[Pn]coverage table, marking each as covered or missing - Report only blocking issues: Logic conflicts, spec gaps, dependency cycles, incomplete Fact changes, Node gaps, specs not end-to-end verifiable
- Do NOT report: Abstraction-level differences, naming style, pseudo-code details
- PRD is the contractual authority -- when in conflict, the PRD wins
Agent Responsibility Boundaries
- Yes: Review PRD and Plan consistency
- Yes: Output traceability matrix and issue list
- No: Do not fix issues (that is
/fix-plan) - No: Do not perform implementation
- No: Do not recommend next steps after completion
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 · 294 lines · 46 tokens per session scan A 1a4d763ce235
review is a skill published in the GitHub repository context4ai/workflow (4 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 3,370 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.