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/fatihkan/badiWrote 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/fatihkan/badi/wp)<a href="https://agentmods.dev/commands/fatihkan/badi/wp"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/wp.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.00000 | $0.00544 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress site management command. Site status, plugin/theme management, security scan, and bulk updates.
Required Tools
- Bash (badi wp commands)
Procedure
Step 1: Check the Site Registry
badi wp list
If the user has registered sites, show them; otherwise suggest adding one:
badi wp add [alias] [url] --method [wp-cli|rest]
Step 2: Site Status
badi wp status [alias]
Shows:
- WordPress version
- Active theme
- Plugin count + pending updates
- Core update status
Step 3: Detailed Review (optional)
badi wp plugins [alias] # Plugin list
badi wp themes [alias] # Theme list
Step 4: Security Scan
badi wp security [alias]
6-point check:
- WP Core freshness
- Plugin updates
- Inactive plugins (removable)
- Is WP_DEBUG off
- Is DISALLOW_FILE_EDIT defined
- The
adminuser and the admin count
Step 5: Bulk Update (Careful!)
badi wp update [alias] all # Core + plugins + themes (120s timeout)
badi wp update [alias] core # Core only
badi wp update [alias] plugins # Plugins only
badi wp update [alias] themes # Themes only
badi wp update [alias] [plugin-name] # A specific plugin
Test on staging; take a backup for production.
Step 6: Follow-up Actions
If security issues exist:
/secret-scan— also search for secrets on the app side/ssl-check [domain]— SSL state/dns-audit [domain]— Email security
Connection Methods
| Method | Scenario |
|---|---|
--method wp-cli --path /var/www/ |
Local WordPress install |
--method wp-cli --ssh user@host |
SSH + remote WP-CLI |
--method rest |
REST API (limited with an interactive password) |
For an application password: WP Admin → Users → Profile → Application Passwords
Example Usage
User: /wp
Assistant: Your registered WP sites: [list]
Which one shall we work on?
User: blog
Assistant: [runs badi wp status blog]
[Interprets the results, suggests a security scan]
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 · 85 lines · 0 tokens per session scan A 4aaa5539c6d8
wp is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 544 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-09-06.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.