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 existential-birds/beagle --skill review-plangit clone --depth 1 https://github.com/existential-birds/beagleWrote 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/existential-birds/beagle/review-plan)<a href="https://agentmods.dev/skills/existential-birds/beagle/review-plan"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/review-plan.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.1 | $0.00021 | $0.02367 |
| Opus 5 | $0.00010 | $0.01184 |
| Sonnet 5 | $0.00004 | $0.00473 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade A, and why
review-plan 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 7d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Plan
Review implementation plans (such as those produced by a plan-writing skill) before execution.
Arguments
- Path: Plan file to review (e.g.,
docs/plans/2025-01-15-auth-feature.md)
Anti-confabulation (gate 0 — runs before every other gate)
Before issuing any verdict — flag a gap, raise an issue, or assign a verdict — you MUST echo the exact artifact you are judging, quoted from a source you read in this turn:
- For a plan finding: the plan step or section text under review, quoted from the plan file read freshly now (not recalled from earlier in the session) — cite the heading or step number it came from.
- For a claim about the codebase the plan touches (a type, API, or file the plan references): the file:line plus cited code, read freshly now.
The artifact is the only source of truth. Never infer what the plan says from the branch name, the working directory, surrounding files, or recollection. If your mental model differs from the freshly read source, the source wins. A verdict issued without a same-turn echo of its target is invalid — emit the echo first, or do not emit the verdict.
This gate exists because an LLM under contextual priming will confidently flag content that is not in the plan. It runs before the hard gates below.
Hard gates (sequence)
Do not skip ahead; each step passes only when the condition is objectively satisfied (artifact path, tool success, or labeled capture—not “I read it mentally”).
- Plan file reachable — Pass: reading
Pathsucceeds; if not, stop and report the missing path. Pass: You can quote or point to where**Goal:**,**Architecture:**, and**Tech Stack:**appear, or you record “header field X absent” as a finding before Step 2. - Skills loaded before reviews — Pass: For each row you will rely on in Step 2’s table, the corresponding skill is loaded (or you record explicit
N/Awith reason, e.g. stack not present). Do not start the Step 3 reviews until this gate passes. - Five reviews captured — Pass: You have five labeled artifacts (one per review lens): pasted outputs, subagent transcripts, or saved snippet files. Pass: Each of the five INVESTIGATE/CHECK/VERIFY prompts has a corresponding response block before Step 4.
- Review file on disk before user prompt — Pass: The file at
[plan-dir]/[plan-basename]-review.mdexists; Pass: reading that path succeeds. Only then run the “Next Steps” / options prompt in Step 5.
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.
- 7d ago First seen · 269 lines · 21 tokens per session scan A 8032574a3fb9
review-plan is a skill published in the GitHub repository existential-birds/beagle (80 stars, last pushed 27d ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,367 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-08-30.
Other skills, from other repositories
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
react-web
React web development with hooks, React Query, Zustand.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.