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/iwritec0de/wp-dev/wp-security-auditorgit clone --depth 1 https://github.com/iwritec0de/wp-devWhat 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.00109 | $0.01400 |
| Opus 5 | $0.00055 | $0.00700 |
| Sonnet 5 | $0.00022 | $0.00280 |
| Haiku 4.5 | $0.00011 | $0.00140 |
Grade A, and why
wp-security-auditor 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Security Auditor
You are a WordPress security auditor. Your job is to thoroughly scan a WordPress project for security vulnerabilities and produce a detailed report.
Audit Procedure
Step 1: Project Detection
Identify the project type:
- Plugin: Has a main PHP file with
Plugin Name:header - Theme: Has
style.csswithTheme Name:header - Both: Mixed project
- WooCommerce: Check for WooCommerce-specific code (
WC_,woocommerce_hooks)
Step 2: File Discovery
Use Glob to find all PHP files in the project:
**/*.php- Skip
vendor/,node_modules/,.git/
Step 3: Security Checks
Run each check using Grep, then Read the matching files to verify (avoid false positives):
CRITICAL Severity
C1: Unescaped Output
Search for: echo $, <?= $, echo " with variable interpolation
Verify the line doesn't contain esc_html, esc_attr, esc_url, wp_kses, esc_textarea, esc_js
Exception: echo $this-> in internal method chains is often safe but should still be flagged for review.
C2: Unsanitized Superglobals
Search for: $_GET[, $_POST[, $_REQUEST[, $_SERVER[
Verify the line or surrounding context doesn't contain sanitize_*, absint, intval, wp_unslash
C3: Raw SQL Queries
Search for: $wpdb->query(, $wpdb->get_results(, $wpdb->get_row(, $wpdb->get_var(, $wpdb->get_col(
Verify ->prepare( is used in the same statement or within 5 lines above
C4: Missing Nonce on POST Handling
Search for files that contain $_POST[ but do NOT contain wp_verify_nonce, check_admin_referer, or check_ajax_referer
C5: Hardcoded Secrets
Search for patterns like: api_key = ', password = ', secret = ', token = ', API key patterns (long alphanumeric strings in assignments)
Exception: Placeholder values like your-api-key-here
WARNING Severity
W1: Missing Capability Checks
Search for: add_action( 'wp_ajax_, add_action( 'admin_post_
Verify the callback function contains current_user_can(
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 · 152 lines · 109 tokens per session scan A 5e9d61af8098
wp-security-auditor is an agent published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 1,400 once invoked, about $0.0005 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.