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/futuregerald/futuregerald-claude-plugin/plan-reviewnpx skills add futuregerald/futuregerald-claude-plugin --skill plan-reviewgit clone --depth 1 https://github.com/futuregerald/futuregerald-claude-pluginWrote 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/futuregerald/futuregerald-claude-plugin/plan-review)<a href="https://agentmods.dev/skills/futuregerald/futuregerald-claude-plugin/plan-review"><img src="https://agentmods.dev/badge/skills/futuregerald/futuregerald-claude-plugin/plan-review.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.00072 | $0.00785 |
| Opus 5 | $0.00036 | $0.00392 |
| Sonnet 5 | $0.00014 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
plan-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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 79 lines · 72 tokens per session scan A 371150ed980a
plan-review is a skill published in the GitHub repository futuregerald/futuregerald-claude-plugin (5 stars, last pushed today), with no licence file. It adds 72 tokens to every session and 785 once invoked, about $0.0004 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 skills, from other repositories
fin-review-loop
经济金融论文的对抗性review循环。对草稿进行多轮严格评审，检查实证严谨性、方法正确性、理论贡献和写作质量，给出可操作的修改建议。（AI review 不能替代同行评审，草稿必须经研究者核实后投稿。）.
challenge
Adversarial review — Fable 5 stress-tests reasoning, Gemini checks knowledge. Use before plan or architecture decisions.
council-of-skills
Use when a proposed skill, workflow, or decision needs adversarial review before it ships: convenes reviewers drawn from the agent-forge registry as hostile personas, adds a BUYER who states plainly whether they would pay, and forces every verdict to include the cheapest 48-hour test that could kill or validate the…
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
local-clawsweeper-review
Run local ClawSweeper exact-item or committed-range reviews without GitHub mutation.