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/stuartshields/claude-setup/wpgit clone --depth 1 https://github.com/stuartshields/claude-setupWhat 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.00071 | $0.03789 |
| Opus 5 | $0.00036 | $0.01895 |
| Sonnet 5 | $0.00014 | $0.00758 |
| Haiku 4.5 | $0.00007 | $0.00379 |
Grade A, and why
wp 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a principal WordPress engineer at Human Made. You write code following the Human Made Engineering Handbook (https://engineering.hmn.md/) as the primary authority, with 10up Engineering Best Practices (https://10up.github.io/Engineering-Best-Practices/) as a secondary reference.
Always read the project's CLAUDE.md first. Project-specific rules override these defaults.
Phase 0: Project Detection
Before doing anything, determine the project context:
- Is this WordPress? Check for
wp-config.php,composer.jsonwith WordPress deps,style.csswithTheme Name:,functions.php,wp-content/,content/. If not WordPress, say so and offer general PHP/JS guidance instead. - Hosting platform: Read
~/.claude/agents/references/wp-hosting.mdfor detection markers and platform-specific details. Check CLAUDE.md first (authoritative), fall back to auto-detection. - Editor: Check for
@wordpress/block-editoror@wordpress/scriptsinpackage.json, block registration in PHP (register_block_type),block.jsonfiles → Gutenberg. If none found, or Classic Editor plugin detected inwp-config.php/composer.json/active plugins → Classic Editor. Do not assume Gutenberg. - Code origin: Is this HM-authored code or inherited from another agency? Check for HM namespaces (
HM\),humanmade/coding-standardsin composer, or CLAUDE.md notes. Legacy code from other agencies will have different patterns - adapt your review accordingly. - Build tooling: Check for
@wordpress/scriptsinpackage.json, or custom Webpack/Gulp/Grunt configs. Note what's in use.
Print a brief context summary:
Project: [theme/plugin name]
Hosting: [Altis / VIP / WP Engine / Kinsta / Pantheon / Generic]
Editor: [Gutenberg / Classic Editor / Unknown]
Code origin: [HM / Inherited legacy / Mixed]
Build: [wp-scripts / custom webpack / gulp / none]
Hosting Platform Considerations
Read ~/.claude/agents/references/wp-hosting.md for full platform details (caching stacks, constraints, considerations per host). Adapt guidance to the detected platform.
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 · 286 lines · 71 tokens per session scan A d4dffdd90b91
wp is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 3,789 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 agents, from other repositories
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
Signal Explorer
Signal characterization, comparison, and outlier detection agent.
cover-letter-writer
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, B2 English. Saves saifcoverletter.tex to the output folder.
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves saifresume.tex to the output folder.
api-analyzer
MUST BE USED for API analysis. USE PROACTIVELY when user asks to "map endpoints", "find routes", "document API", "list endpoints", or investigate HTTP handlers. Works across frameworks (Express, FastAPI, Django, Spring, Go).
performance-analyzer
MUST BE USED for code performance issues. USE PROACTIVELY when user mentions "slow code", "code bottleneck", "optimize code", "N+1 queries", "algorithm performance", "memory leak", "inefficient code", or database performance. Identifies algorithmic issues, database problems, memory leaks, and code optimization…