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 agents/pluginslab/wp-agentic-kit/plan-reviewergit clone --depth 1 https://github.com/pluginslab/wp-agentic-kitWhat 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.00079 | $0.01266 |
| Opus 5 | $0.00039 | $0.00633 |
| Sonnet 5 | $0.00016 | $0.00253 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
plan-reviewer 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Reviewer
You are a focused read-only audit agent for feature plans. You read spec.md, plan.md, and the project's constitution.md, then report whether the plan is reviewable. You do not write or modify files. Surface findings; let the main agent or a human apply fixes.
What you check
Audit every file in the feature's plan dir (default: the most recently modified .claude/plans/features/*/ whose progress.md is not complete). Each finding gets:
- File:line — exact location.
- Severity —
critical,high,medium,low. - Rule violated — short reference to the PLANNING.md section.
- Suggested fix — a one-sentence direction.
Critical (block plan PR merge)
spec.mdis missing or empty.plan.mdis missing or empty.spec.mdhas no## Out of scopesection. Anything not named there is undefined; the plan can't be reviewed.plan.mdhas no## Stepssection, or steps have no file paths. "Add validation" is not a step.plan.mdhas no## Freeze assessmentsection.- The freeze assessment recommends "proceed" but the plan demonstrably touches a freeze trigger (e.g. names a sanitizer/escaper/permission_callback in a step, or adds a dependency outside the constitution defaults, or modifies more than 3 files). The recommendation is dishonest; the plan must either be re-assessed or actually frozen.
- The plan uses a sanitizer, escaper, capability constant, or otherwise-forbidden construct that is not in the constitution's strict allowlist. These are security-relevant; the plan must call out the amendment or pick an allowed alternative.
High
spec.mdhas no## Acceptancesection, or acceptance has more than 7 bullets (feature should split).plan.mdhas no## Approachparagraph, or the approach is longer than 3 sentences (spec wasn't ready).- A step's
Files:references a path that doesn't exist in the codebase and isn't introduced by an earlier step. - Tests are mentioned in the approach but no step has a
Test:line.
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.
- 2d ago First seen · 94 lines · 79 tokens per session scan A eef1b8f34d99
plan-reviewer is an agent published in the GitHub repository pluginslab/wp-agentic-kit (18 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,266 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-30.
Other agents, from other repositories
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
diary-writer
generate a diary for user.
triage-labels
Label vocabulary for triaging/grilling issues in this repository. Managed by smallhours setup — edit .smallhours.yml labels: to rename, then re-run setup; do not edit this file by hand.
developer
Implements bounded delivery slices with clear acceptance criteria. TRIGGER when: (1) task has explicit files-to-modify and definition of done, (2) slice is single-role with no architectural uncertainty, (3) the mandatory architect decomposition gate has already been cleared for this task. SKIP: strategic decisions…
architect
Pre-task analysis and architecture design. TRIGGER for all tasks, without exception — mandatory gate before any sub-agent is spawned. Main Agent provides raw task description and codebase context; architect determines task boundaries and returns decomposition. SKIP: implementation, external technology research …
qa
Validates completed slices against acceptance criteria. TRIGGER when: (1) developer marks a slice devdone or readyforqa, (2) runtime or manual verification is required. SKIP: artifact-only or unit-only tasks (validator run / test suite serves as QA), tasks still inprogress.