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 commands/heznpc/ploidy/review-prgit clone --depth 1 https://github.com/heznpc/PLOIDYWrote 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/commands/heznpc/ploidy/review-pr)<a href="https://agentmods.dev/commands/heznpc/ploidy/review-pr"><img src="https://agentmods.dev/badge/commands/heznpc/ploidy/review-pr.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.00043 | $0.01253 |
| Opus 5 | $0.00022 | $0.00626 |
| Sonnet 5 | $0.00009 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
review-pr 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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user wants a second-opinion review on a pull request before merging.
If $ARGUMENTS is empty, target the current branch's PR; if it's a
number or #N, target that PR on the configured remote.
1 · Gather the PR payload
Decide the target:
- If
$ARGUMENTSis blank →gh pr view --json title,body,author,headRefName,baseRefName,urlfor the current branch. - If
$ARGUMENTSis a number →gh pr view $ARGUMENTS --json title,body,author,headRefName,baseRefName,url.
Then capture the diff:
gh pr diff <target>— limit to ~3000 lines for the fresh payload. If larger, keep the full diff for the Deep step and pass a<head>+<tail>+<... N lines elided ...>truncation to the Fresh sub-agent.
Store:
pr_title,pr_body,pr_url,base_ref,head_refdiff_full(for Deep),diff_compact(for Fresh)
2 · Write the Deep-context review
You have the full repo. In ~250 words:
- Stated goal check — does the diff actually achieve what the PR body claims? Quote the specific claim and mark match / partial / mismatch.
- Scope discipline — is anything in the diff unrelated to the stated goal? Flag each file that looks scope-creeping.
- Over-engineering — are there abstractions, generalisations, or tests added "because we always do that" rather than needed for this change? Name them. If none, say so.
- Coverage gaps — given your knowledge of the repo, what didn't
get touched that probably should have? (migrations, docs,
CONVENTIONS.md, call sites elsewhere, …) - Author-bias check — what in the PR author's decisions do you find yourself defending because you also would have written it that way? Name it explicitly. If nothing, say so.
Tag each finding HIGH / MEDIUM / LOW.
3 · Spawn a Fresh sub-agent
Use the Agent tool (subagent_type="general-purpose"). The fresh
reviewer must see only the PR description + the (possibly truncated)
diff — no repo context, no CLAUDE.md, no prior
conversation.
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.
- 4d ago First seen · 131 lines · 0 tokens per session scan A 44bbc18ede0a
review-pr is a command published in the GitHub repository heznpc/PLOIDY (0 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 1,253 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.