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 skills add amElnagdy/review-skills --skill debate-reviewgit clone --depth 1 https://github.com/amElnagdy/review-skillsWrote 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/amelnagdy/review-skills/debate-review)<a href="https://agentmods.dev/skills/amelnagdy/review-skills/debate-review"><img src="https://agentmods.dev/badge/skills/amelnagdy/review-skills/debate-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amelnagdy/review-skills/debate-review"><img src="https://agentmods.dev/badge/skills/amelnagdy/review-skills/debate-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
- Socket warn
- Snyk warn
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.1 | $0.00053 | $0.01014 |
| Opus 5 | $0.00026 | $0.00507 |
| Sonnet 5 | $0.00011 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
debate-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 13d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
debate-review
Two models argue before anything is posted. A main reviewer finds issues. A debate reviewer tries to
knock them down and may add its own. The main reviewer then makes the final call, and one review with
inline comments lands on the PR or MR. It posts from the user's own gh, glab or az account as a
non-approval review or comment. It never approves and never requests changes.
You are the orchestrator. You run one command and relay the result. You do not review the diff yourself, and you do not touch the PR.
Run it
node "<skill-dir>/scripts/review-pr.mjs" --local [--base <ref>]
node "<skill-dir>/scripts/review-pr.mjs" <pr-url | number> [--dry-run]
- If the user wants a review and there is no PR/MR URL, run
--localfrom the repo (or--repo-dir). Do not invent a URL. Relay stdout.--localnever talks to a forge and rejects non-UTF-8 Git paths rather than decoding them lossily. <pr-url>is a GitHub/pull/N, GitLab/-/merge_requests/N, or Azure DevOps/_git/<repo>/pullrequest/NURL (dev.azure.comor the legacy*.visualstudio.com). A bare number resolves against the cwd'sorigin, including Azure DevOps https andssh.dev.azure.com:v3/remotes.--dry-runprints a live PR review instead of posting it. It does not combine with--local.- Azure DevOps needs
azlogged in (az login) with access to the project. No extension is required, the script talks to the REST API throughaz rest. A review there is N inline comment threads plus one closed summary thread, since Azure DevOps has no single review object; the alert blockquotes render as plain quotes, which still read. - The reviewers are two delegate-skills lanes,
review-mainandreview-debate. If either is missing the script says so. Add them withdelegate-setup. Pick two different implementers, since the debate is only worth something when the second model doesn't share the first one's blind spots (mainclaudeorgrok, debatecodexat high effort is a good pair). For a one-off, pass--main <implementer>or--debate <implementer>. Only implementers whose relay has--read-onlyare accepted. These two lanes belong to the reviewer. Don't point them at a lane you use for other work, such as a plan-debate lane. - Exit code
3means this head sha already has a debate-review. Re-run with--forceto post again. - A run takes minutes, since it is two or three implementer sessions back to back. Run it in the background and report the printed URL when it finishes. Don't poll tightly.
What ships with it
13 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.
- assets/prompts/review-debate.md 2.9 KB
- assets/prompts/review-main.md 4.2 KB
- assets/prompts/review-rebuttal.md 2.7 KB
- references/comment-format.md 2.3 KB
- references/schema.md 3.9 KB
- scripts/lib/diff.mjs 2.1 KB runs code
- scripts/lib/dispatch.mjs 4.7 KB runs code
- scripts/lib/forge.mjs 18 KB runs code
- scripts/lib/local.mjs 19 KB runs code
- scripts/lib/render.mjs 2.6 KB runs code
- scripts/lib/shell.mjs 1.0 KB runs code
- scripts/lib/validate.mjs 5.2 KB runs code
- scripts/review-pr.mjs 19 KB runs code
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.
- 13d ago First seen · 63 lines · 53 tokens per session scan A af0dce8aa6ac
debate-review is a skill published in the GitHub repository amElnagdy/review-skills (108 stars, last pushed 17d ago), licensed MIT. It adds 53 tokens to every session and 1,014 once invoked, about $0.0003 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
agent-watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
agent-design-best-practices
Best practices for designing Claude Code agent files (.claude/agents/.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official…
graphify-dotnet
Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and…
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…
sonarqube-mcp
Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…