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/pluginslab/wp-agentic-kit/audit-plangit 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.00030 | $0.00320 |
| Opus 5 | $0.00015 | $0.00160 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
audit-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 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.
What it actually says
Audit plan
Dispatch the plan-reviewer sub-agent to audit a feature plan before human review.
- If
$ARGUMENTSis empty, locate the active feature: the most recently modified.claude/plans/features/*/progress.mdwhosestatus:is notcomplete|done|shipped|archived|completed. Use its directory's basename as the slug. - If
$ARGUMENTSis non-empty, use it as the slug. Verify.claude/plans/features/$ARGUMENTS/exists. - Invoke the
plan-reviewersub-agent with this instruction:Audit
.claude/plans/features/<slug>/. Check spec.md, plan.md, findings.md (if present), and constitution.md per the rules in.claude/agents/plan-reviewer.md. Report findings grouped by severity. - Surface the report back to me grouped by severity (Critical / High / Medium / Low).
- If Critical findings exist: tell me which ones and stop — they need fixing before the plan PR can be merged.
- If only Medium/Low findings exist: list them and ask whether to fix now or merge anyway.
- If clean: confirm the plan is ready for human review and (if a plan PR isn't open yet) offer to run
/plan-freeze.
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 · 18 lines · 30 tokens per session scan A 78870a67a014
audit-plan is a command published in the GitHub repository pluginslab/wp-agentic-kit (18 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 320 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-30.
Other commands, from other repositories
respond-to-issue
Respond to an issue triggered by @elixpoo mention or the ELIXPO label.
commit-push-pr
Commit, push, and open a PR. Branch rules prevent accidents on main or duplicate PRs.
fill-pr-description
Generate a PR description from the diff. Triggered when a whitelisted author puts @elixpoo fill in the PR body.
review
Command "review" from elixpo/claudeOps.elixpo, covering what to look at, don't, output format, issues and suggestions.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.