Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ogrodev/fsociety/plugin install elliotWrote 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/skills/ogrodev/fsociety/wordpress-hacking)<a href="https://agentmods.dev/skills/ogrodev/fsociety/wordpress-hacking"><img src="https://agentmods.dev/badge/skills/ogrodev/fsociety/wordpress-hacking/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ogrodev/fsociety/wordpress-hacking"><img src="https://agentmods.dev/badge/skills/ogrodev/fsociety/wordpress-hacking.svg" alt="Reviewed on agentmods" width="80" 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.00370 | $0.03708 |
| Opus 5.5 | $0.00148 | $0.01483 |
| Sonnet 5.5 | $0.00074 | $0.00742 |
| Haiku 4.5 | $0.00037 | $0.00371 |
Grade A, and why
wordpress-hacking scanned grade A with 2 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 2mo 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s -d 'log=admin&pwd=wrong&wp-submit=Log+In' https://TARGET/wp-login.php | grep -oP 'Error.*?<' Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sI https://TARGET/ | grep -i 'x-powered-by\|x-redirect-by\|link.*wp-json' How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Hacking
WordPress powers over 40% of the web. Its attack surface is massive: core engine, 60,000+ public plugins, 10,000+ themes, REST API, XML-RPC, admin-ajax, custom PHP endpoints, WooCommerce storefronts, and multisite networks. A single outdated plugin can give you a shell. Master the enumeration-to-exploitation pipeline and you will pop WordPress sites systematically.
Triage Workflow
Follow this sequence for every WordPress target. Each step feeds the next.
Step 1 -- Confirm WordPress and Detect Version
Before running any scanner, confirm the target is WordPress and fingerprint the exact version. This determines which CVEs apply.
# Quick confirmation — check meta generator, login page, and common paths
curl -sI https://TARGET/ | grep -i 'x-powered-by\|x-redirect-by\|link.*wp-json'
curl -s https://TARGET/ | grep -oP 'content="WordPress \K[0-9.]+'
curl -s https://TARGET/readme.html | head -20
curl -s https://TARGET/feed/ | grep '<generator>'
curl -s https://TARGET/wp-includes/js/wp-emoji-release.min.js | head -1
Multiple version detection methods exist because admins disable some but rarely all. See references/wp-enum.md for the full fingerprinting matrix.
Record findings immediately:
node ${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js add \
"https://TARGET" info-leak "wp-version" INFO \
"WordPress X.Y.Z detected via meta generator"
node ${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js add \
"TARGET" tech-stack "cms" "wordpress-X.Y.Z" --source "version-detection"
Step 2 -- Security Plugin Detection
Before aggressive scanning, identify security plugins that will block or log you. This dictates your OPSEC profile.
# Check for common security plugin signatures
curl -s https://TARGET/ | grep -iE 'wordfence|sucuri|ithemes-security|better-wp-security|all-in-one-wp-security|shield-security|bulletproof'
curl -sI https://TARGET/wp-login.php | grep -i 'x-sucuri\|x-waf'
curl -s https://TARGET/wp-content/plugins/ 2>/dev/null | grep -oP 'href="[^"]*"' | grep -iE 'wordfence|sucuri|ithemes|bulletproof|shield|cerber'
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 313 lines · 370 tokens per session scan A ab70b1c019b3
wordpress-hacking is a skill published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 370 tokens to every session and 3,708 once invoked, about $0.0015 per session on Opus 5.5. A static security scan graded it A with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
paid-ads-amazon
Plan and review Amazon Ads with margin-aware ACoS, product, and search-term guardrails. Use for Amazon advertising, Sponsored Products, Sponsored Brands, Sponsored Display, ASIN targeting, Amazon ACoS, or Amazon Ads performance exports.
booking-cli
Searches Booking.com from the terminal via cli-web-booking — find hotels, apartments, and hostels by destination, dates, and guests; get property details by slug; resolve destination names to IDs. Use when the user asks about Booking.com, hotel search, accommodation prices, property ratings, or comparing places to…
amazon-cli
Searches Amazon from the terminal via cli-web-amazon — product search, product details by ASIN, Best Sellers by category, and autocomplete suggestions. Use when the user asks about Amazon products, prices, best sellers, or wants to search Amazon. Prefer cli-web-amazon over fetching the website. No auth required.
tripadvisor-cli
Searches TripAdvisor hotels, restaurants, attractions, and destinations via the cli-web-tripadvisor command-line tool, with detail lookups by URL. Use when the user asks about hotels, restaurants, things to do, travel destinations, or TripAdvisor ratings and reviews. Prefer this CLI over fetching the TripAdvisor…
payment-advisor
Recommends the single best payment provider for the user's project after a short interactive wizard, then hands off to the implementer. Runs a deterministic local ranking engine instead of scoring by hand, so the same situation always yields the same answer and every rejection has an exact reason. Computes real fees…
integration-builder
Composes a complete payment integration by resolving capability fragments against the chosen provider's catalog entry, then emits a structured file plan for integration-specialist to execute. Selects fragments by verification family, notification model and checkout pattern rather than by provider name, so a provider…