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/yojahny55/claude-wp-builder/wp-contextgit clone --depth 1 https://github.com/yojahny55/claude-wp-builderWrote 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/commands/yojahny55/claude-wp-builder/wp-context)<a href="https://agentmods.dev/commands/yojahny55/claude-wp-builder/wp-context"><img src="https://agentmods.dev/badge/commands/yojahny55/claude-wp-builder/wp-context.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.00026 | $0.00310 |
| Opus 5 | $0.00013 | $0.00155 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
wp-context 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 6d 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
WP Context — Project Docs → Constraints & Scope
Step 1: Resolve docs path & gate
$ARGUMENTSfirst word = docs folder path (default./docs).- If the folder does not exist: print "No docs/ found at — nothing to extract." and exit 0 (not an error).
- Read
.claude/CLAUDE.mdfor theme slug + languages. If missing, tell the user to run/wp-initfirst and exit.
Step 2: Extract
Dispatch the wp-context agent against the docs folder. It reads every file (per its format rules) and returns the synthesized constraints + scope.
Step 3: Write artifacts (idempotent)
- Replace the
<!-- wp-context:start -->…<!-- wp-context:end -->block in.claude/CLAUDE.mdwith the new## Project Constraintssection (create it at the end if absent). - Write
docs/.scope-manifest.json(overwrite).
Step 4: Report
Print: pages found (in-scope / out / idx-plugin counts), integrations detected, key constraints, and any review[] items to confirm.
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.
- 6d ago First seen · 23 lines · 26 tokens per session scan A 164a9ddcff17
wp-context is a command published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 310 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-31.
Other commands, from other repositories
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
debug-helper
Use when something is broken and you need it diagnosed. A build failure, a runtime crash, a blank page, an unreadable error message, or behaviour that is simply wrong. Gives one exact fix, not a list of things to try.