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 skills add Lonsdale201/wp-agent-skills --skill lw-firewall-rate-limit-workergit clone --depth 1 https://github.com/Lonsdale201/wp-agent-skillsWrote 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/lonsdale201/wp-agent-skills/lw-firewall-rate-limit-worker)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/lw-firewall-rate-limit-worker"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-firewall-rate-limit-worker/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/lonsdale201/wp-agent-skills/lw-firewall-rate-limit-worker"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-firewall-rate-limit-worker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00142 | $0.03755 |
| Opus 5 | $0.00071 | $0.01878 |
| Sonnet 5 | $0.00028 | $0.00751 |
| Haiku 4.5 | $0.00014 | $0.00376 |
Grade A, and why
lw-firewall-rate-limit-worker 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LW Firewall rate-limit worker compatibility
Use this skill when an endpoint may be blocked by LW Firewall or needs a
dedicated limit. The copied MU worker runs on muplugins_loaded priority 1,
before normal plugin callbacks.
Worker decision order
After bootstrap/version checks, the request path is:
LW_FIREWALL_DISABLE_WORKERand masterenabledexits.- Worker heartbeat transient (
lw_firewall_worker_alive), written before any decision so the Status tab can tell "installed" from "actually running". - Server/localhost IP exemption.
ip_whitelistexemption.ip_blacklist403.- Geo blocking.
- Storage resolution (memoized per request).
- Shared-ban lookup — unconditional whenever the firewall is on since 1.5.5.
- 404-flood lookup.
- User-Agent bot blocking.
- Endpoint detection.
- Per-IP counter, 429/redirect, and optional violation escalation.
Whitelisting bypasses every later worker check. A blacklist or geo block runs before endpoint-specific code.
The server-IP exemption covers 127.0.0.1, ::1 and SERVER_ADDR only. Since
1.5.6 the site's own hostname is deliberately not resolved into an
exemption: SERVER_NAME comes from the client's Host header under Apache's
default UseCanonicalName Off, so resolving it was a full bypass for any
address an attacker could point a hostname at.
Exact endpoint detection
Since 1.5.6 classification runs on the decoded path, never the raw URI.
lw_firewall_parse_uri() splits path from query, rawurldecode()s the path,
collapses repeated slashes and strips a trailing one; lw_firewall_path_is()
then compares with str_ends_with so a subdirectory install's
/blog/wp-login.php still matches.
| Reason | v1.5.6 condition |
|---|---|
cron |
decoded path is/ends with /wp-cron.php, protect_cron; exempt only when doing_wp_cron is a query arg on that path |
xmlrpc |
decoded path is/ends with /xmlrpc.php, protect_xmlrpc |
login |
decoded path is/ends with /wp-login.php, protect_login |
rest |
decoded path contains /wp-json/ (bare /wp-json included) or a rest_route query arg is present, protect_rest_api |
filter |
raw query string contains a configured filter_params substring |
What ships with it
1 file 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.
- 9d ago First seen · 319 lines · 142 tokens per session scan A 94deab03ea7c
lw-firewall-rate-limit-worker is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session and 3,755 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
wp-plugin-development
Architecture and development guidelines for WordPress plugins published on wordpress.org: file structure, plugin header, lifecycle hooks, Settings API, admin UI, escaping helpers for admin JavaScript, default values and option migrations, multisite-shared resources, custom post types, custom database tables…
wp-plugin-performance
Performance guidelines for WordPress plugin development: database optimization, object caching, conditional asset loading, efficient hooks, HTTP requests, WP-Cron, AJAX/REST optimization, and common anti-patterns. Based on official WordPress Developer Resources and WP VIP documentation.
build-mcp-server
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development — it interrogates…
data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the API. Don't use for implementing audience…
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
new
Create a new project to start development quickly.