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/random6913/claude-code-superkit/review-orchestratornpx skills add RaNDoM6913/claude-code-superkit --skill review-orchestratorgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/review-orchestrator)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/review-orchestrator"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/review-orchestrator.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 | $0.00028 | $0.01291 |
| Opus 5 | $0.00014 | $0.00646 |
| Sonnet 5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
review-orchestrator 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 today.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unified Orchestrated Code Review
Detect changed files, enrich with git context, dispatch the right reviewer agents in parallel, collect and deduplicate findings.
Target
Parse the user's request to determine scope and parameters. Accepted formats:
PR#NNNor a number — review a pull request- A branch name — diff against that branch
--full— review all tracked files- Empty — default to
HEAD~1
Step 1 — Detect Changed Files and Gather Context
Determine the diff base:
- If target matches
PR#NNNor is a number:gh pr diff $TARGET --name-only - If target is a branch name:
git diff --name-only $TARGET...HEAD - If target is
--full: review all tracked files (git ls-files) - If empty:
git diff --name-only HEAD~1
Gather structured context for agent prompts:
# Changed files with line counts
git diff --stat ${BASE}...HEAD
# Full diff hunks (for agent context injection)
git diff ${BASE}...HEAD
# Recent 5 commits (for intent)
git log --oneline -5
Build a REVIEW_CONTEXT block:
=== REVIEW CONTEXT ===
## Changed Files (N files, +X/-Y lines)
<git diff --stat output>
## Recent Commits (intent)
<git log --oneline -5>
## Diff Hunks
<full diff, truncated to 8000 chars per agent if needed>
=== END CONTEXT ===
Step 2 — Map Files to Agents
Based on file extension and path patterns, build a dispatch plan. Each pattern maps to one or more agents:
| File Pattern | Agents |
|---|---|
*.go (excluding *_test.go, migrations/) |
go-reviewer, security-scanner |
migrations/*.sql or db/migrate/*.sql |
migration-reviewer |
*.tsx |
ts-reviewer, design-system-reviewer |
*.ts |
ts-reviewer |
*.py |
py-reviewer, security-scanner |
*.rs |
rs-reviewer |
**/bot*/**/*.go or **/bot*/**/*.py |
bot-reviewer |
*.yaml / *.yml (OpenAPI/config) |
api-contract-sync (if available) |
Rules:
- A single agent is dispatched at most once even if multiple files match
- Only dispatch agents that are actually available in the project's skills directory
- If no files match any pattern, report "No reviewable changes detected" and stop
- List the dispatch plan before executing (agent name + matched file count)
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.
- today First seen · 153 lines · 28 tokens per session scan A 4285b92933b5
review-orchestrator is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,291 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…