recursive-review-bundle

A command for creating a structured code-review package for a particular software-run phase. The package gathers the plan, requirements, implementation summary, routing details, and review questions.

In plain words
What is it for?
Use it to prepare review evidence and request findings ordered by severity for a coding-agent run.
Why use it?
It gives a reviewer the context needed to check whether the implementation matches the plan and whether any requirements remain unfinished.

Command

Install

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.

agentmods
npx agentmods add commands/try-works/recursive-mode/recursive-review-bundle
Clone the repo
git clone --depth 1 https://github.com/try-works/recursive-mode
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 911 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00911
Opus 5 $0.00000 $0.00456
Sonnet 5 $0.00000 $0.00182
Haiku 4.5 $0.00000 $0.00091

Measured 2d ago against content hash 0d958cc10c1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

docs/templates/commands/recursive-review-bundle.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

recursive-review-bundle (prompt template)

Paste this into chat if your agent does not support custom slash commands.

Usage Pattern

Generate a recursive review bundle for run <run-id> phase 03.5 using the canonical bundle format.
python "<SKILL_DIR>/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" --upstream-artifact "/.recursive/run/<run-id>/03-implementation-summary.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?" --audit-question "Which changed files drift from the plan?" --required-output "Findings ordered by severity"

pwsh -NoProfile -File "<SKILL_DIR>/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","/.recursive/run/<run-id>/03-implementation-summary.md" -PriorRef "/.recursive/memory/MEMORY.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?","Which changed files drift from the plan?" -RequiredOutput "Findings ordered by severity"

Example for a Phase 4 test-review bundle:

python "<SKILL_DIR>/scripts/recursive-review-bundle.py" --repo-root . --run-id "<run-id>" --phase "04 Test Summary" --role tester --artifact-path "/.recursive/run/<run-id>/04-test-summary.md" --upstream-artifact "/.recursive/run/<run-id>/02-to-be-plan.md" --upstream-artifact "/.recursive/run/<run-id>/03-implementation-summary.md" --evidence-ref "/.recursive/run/<run-id>/evidence/logs/green/tests.log" --audit-question "Are the executed tests sufficient for the changed behavior?" --required-output "Audit recommendation"

Read the full file on GitHub · 56 lines

Changes

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.

  1. 2d ago First seen · 56 lines · 0 tokens per session scan A 0d958cc10c1b

Subscribe to this mod's changes

recursive-review-bundle is a command published in the GitHub repository try-works/recursive-mode (129 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 911 tokens. 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.