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/try-works/recursive-mode/recursive-review-bundlenpx skills add try-works/recursive-mode --skill recursive-review-bundlegit clone --depth 1 https://github.com/try-works/recursive-modeWhat 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.00049 | $0.00827 |
| Opus 5 | $0.00024 | $0.00413 |
| Sonnet 5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
recursive-review-bundle 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recursive-review-bundle
Use this skill to prepare a canonical review bundle before delegating an audit or review in recursive-mode.
This skill does not replace /.recursive/RECURSIVE.md. It packages the context bundle that delegated reviewers need so the review is durable, reproducible, and acceptable to the workflow.
Canonical Scripts
Use the repo scripts:
./.recursive/scripts/recursive-review-bundle.py./.recursive/scripts/recursive-review-bundle.ps1
Prefer the Python script when both toolchains are available. Use the PowerShell wrapper when the delegated path is already PowerShell-oriented.
Minimum Inputs
Provide all of:
- repo root
- run id
- phase name
- reviewer role
- artifact path being reviewed
- exact upstream artifact paths
- relevant audit questions
- required output shape
Add explicit evidence refs or addenda when they matter. The bundle generator will also auto-discover relevant addenda and skill-memory refs when applicable.
Typical Commands
python ./.recursive/scripts/recursive-review-bundle.py \
--repo-root . \
--run-id "<run-id>" \
--phase "03.5 Code Review" \
--role code-reviewer \
--artifact-path "/.recursive/run/<run-id>/03.5-code-review.md" \
--upstream-artifact "/.recursive/run/<run-id>/00-requirements.md" \
--upstream-artifact "/.recursive/run/<run-id>/02-to-be-plan.md" \
--routing-config-path ".recursive/config/recursive-router.json" \
--routing-discovery-path ".recursive/config/recursive-router-discovered.json" \
--routed-cli "codex" \
--routed-model "gpt-5.4" \
--audit-question "Which R# remain incomplete?" \
--required-output "Findings ordered by severity"
pwsh -NoProfile -File ./.recursive/scripts/recursive-review-bundle.ps1 `
-RepoRoot . `
-RunId "<run-id>" `
-Phase "03.5 Code Review" `
-Role code-reviewer `
-ArtifactPath "/.recursive/run/<run-id>/03.5-code-review.md" `
-UpstreamArtifact "/.recursive/run/<run-id>/00-requirements.md","/.recursive/run/<run-id>/02-to-be-plan.md" `
-RoutingConfigPath ".recursive/config/recursive-router.json" `
-RoutingDiscoveryPath ".recursive/config/recursive-router-discovered.json" `
-RoutedCli "codex" `
-RoutedModel "gpt-5.4" `
-AuditQuestion "Which R# remain incomplete?" `
-RequiredOutput "Findings ordered by severity"
What ships with it
1 file 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 · 92 lines · 49 tokens per session scan A 5993011799f3
recursive-review-bundle is a skill published in the GitHub repository try-works/recursive-mode (129 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 827 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-30.
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.