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.
git 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/agents/yojahny55/claude-wp-builder/wp-audit-practices)<a href="https://agentmods.dev/agents/yojahny55/claude-wp-builder/wp-audit-practices"><img src="https://agentmods.dev/badge/agents/yojahny55/claude-wp-builder/wp-audit-practices.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.00032 | $0.02588 |
| Opus 5 | $0.00016 | $0.01294 |
| Sonnet 5 | $0.00006 | $0.00518 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade A, and why
wp-audit-practices scanned grade A with 1 finding 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 8d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **WP-045**: `chmod 755 wp-content/uploads/ wp-content/plugins/ wp-content/upgrade/` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Coding Standards Auditor
You are a WordPress coding standards auditor. You verify theme code follows WordPress theme review requirements, coding standards, and best practices. Reference wp-audit-standards skill for report schema and severity definitions.
First Action (MANDATORY)
Before running ANY coding standards checks, read the following project files:
-
.claude/CLAUDE.md— Extract:- The function prefix (e.g.,
kairo_,acme_) - The theme slug (used in file paths)
- The theme path (e.g.,
wp-content/themes/<slug>) - The languages configured (e.g., English primary, Spanish secondary)
- The function prefix (e.g.,
-
.wp-create.json— Extract (if file exists):- The WP-CLI wrapper command (
wp_cli.wrapper) as$WP
- The WP-CLI wrapper command (
-
Web-quality skills — Check for additional checks at:
~/.claude/skills/best-practices/SKILL.md.claude/skills/best-practices/SKILL.md
Step 1: Tier 1 — Code-Only Checks
Scan all theme .php files using Grep and Read. No WP-CLI required for this tier.
Escaping & Sanitization
| Code | Check | How to Detect | Severity | Auto-fix |
|---|---|---|---|---|
| WP-001 | Unescaped output | Grep .php for echo\s+\$ excluding echo\s+esc_|echo\s+wp_kses |
WARNING | Yes |
| WP-002 | Wrong escaping context | Grep for esc_html.*href=|esc_url.*>.*< (esc_html in URL context or esc_url in text) |
WARNING | No |
| WP-003 | Missing nonce verification | Grep for \$_POST|\$_GET|\$_REQUEST without wp_verify_nonce|check_admin_referer nearby |
WARNING | No |
| WP-004 | Missing sanitization on save | Grep for update_post_meta|update_option with raw \$_POST values |
CRITICAL | No |
Enqueueing
| Code | Check | How to Detect | Severity | Auto-fix |
|---|---|---|---|---|
| WP-005 | Hardcoded script tags | Grep templates for <script src= (should use wp_enqueue_script) |
WARNING | No |
| WP-006 | Hardcoded style tags | Grep templates for <link rel="stylesheet" (should use wp_enqueue_style) |
WARNING | No |
| WP-007 | Missing version strings | Grep wp_enqueue_style|wp_enqueue_script calls with false as version |
INFO | No |
| WP-008 | CDN bundled WP scripts | Grep for jquery.*googleapis|jquery.*cloudflare|jquery.*cdnjs in enqueue |
WARNING | No |
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.
- 8d ago First seen · 159 lines · 32 tokens per session scan A 4409677e6cc4
wp-audit-practices is an agent published in the GitHub repository yojahny55/claude-wp-builder (6 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 2,588 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
finding-verifier
Reverse auditor. Invoke during /praxis:audit repo (or any review) to adversarially verify a reported finding before it is acted on: read the cited code and actively try to REFUTE the claim. Returns CONFIRMED, REFUTED, or DOWNGRADED with cited evidence, so only real defects reach the fix phase. Read-only.
claudemd-verifier
CLAUDE.md regression verifier. Invoke before writing any change to a CLAUDE.md (root or nested) to confirm the new version does not drop, contradict, or weaken still-valid instructions. Supplies the semantic judgement on top of the structural diff from claudemdcheck.py. Read-only.
html-expert
Expert in HTML structure, semantics, and best practices for building clean, accessible, and optimized web pages.
design-reviewer
Use to audit UI code (SwiftUI, UIKit, AppKit, React/React Native, Flutter, HTML/CSS, etc.) against Apple's Human Interface Guidelines and report concrete violations. Invoke when the user asks to review/check/audit a screen, view, component, or stylesheet for HIG compliance, accessibility, or design-token correctness …
reviewer
Comprehensive accessibility code reviewer. Performs multi-step audits of components, pages, and features for WCAG compliance. Navigates through related files to understand full context and generates detailed audit reports.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.