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/readmegit 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.00000 | $0.00659 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
README 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 yesterday.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.claude/agents/
Sub-agents the main Claude Code agent can delegate to. Each one runs in its own context window, with its own restricted tool set, so the main agent stays focused.
Maps to the talk's framework
Discernimento. Sub-agents are the discernment D — independent, narrow-scope judgement before a human signs off. Read-only by design: they surface what a human should know, never apply fixes.
Why use a sub-agent
The kit's bar for shipping a sub-agent: it has to do something a skill can't. In practice that means either tool restriction (the sub-agent literally can't call Edit / Write) or context isolation for work that would otherwise dump thousands of lines into the main agent's window.
A "specialist who writes blocks" or "specialist who writes REST endpoints" doesn't clear that bar — it's a skill in disguise. So the kit ships exactly two sub-agents, both read-only audits.
Shipped sub-agents
| Sub-agent | Tools | When to invoke |
|---|---|---|
plan-reviewer |
Read, Grep, Glob, Bash | During Phase 2.5 of wordpress-feature, after scripts/open-plan-pr.sh opens the plan PR. Audits spec + plan against PLANNING.md and the constitution. |
security-reviewer |
Read, Grep, Glob, Bash | Before merging a feature PR, before a release, after any change to input handling. |
Block and REST work is handled by the wp-block-development and wp-rest-api skills the kit pulls from WordPress/agent-skills into .claude/skills/ — those run on the main agent's context, no handoff needed.
How invocation works
Inside Claude Code:
> use the security-reviewer subagent to audit the changes on this branch
The main agent recognizes the sub-agent name, spawns it with its own context, and reports back when it finishes.
Adding your own
- Drop a markdown file in this directory.
- Frontmatter requires
name,description, andtools(comma-separated list). - The body is the sub-agent's system prompt — keep it focused. One job, one playbook.
- Reference shared knowledge via
@.claude/references/...paths so sub-agents and the main agent share the same source of truth.
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.
- yesterday First seen · 50 lines · 0 tokens per session scan A 30278aafbf3f
README is an agent published in the GitHub repository pluginslab/wp-agentic-kit (18 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 659 tokens. 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.