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-password-reset-protectiongit 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-password-reset-protection)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/lw-firewall-password-reset-protection"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-firewall-password-reset-protection/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-password-reset-protection"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-firewall-password-reset-protection.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.00123 | $0.02091 |
| Opus 5 | $0.00062 | $0.01045 |
| Sonnet 5 | $0.00025 | $0.00418 |
| Haiku 4.5 | $0.00012 | $0.00209 |
Grade A, and why
lw-firewall-password-reset-protection 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LW Firewall password-reset protection
LW Firewall 1.5.1 added a reset-specific guard. Use this skill before changing
a lost-password form, calling retrieve_password() from a custom transport, or
tuning the reset limits.
Activation and hook boundary
The reset guard initializes only when the MU worker is current, master
enabled is true, and reset_protect_enabled is true. It registers:
| Hook | Role |
|---|---|
lostpassword_form |
render lw_fw_reset_token and lw_fw_confirm_url on core wp-login.php |
lostpassword_post |
apply proof decision and three rate-limit axes before mail |
allow_password_reset |
optionally refuse every privileged account when reset_block_admins is on |
Core retrieve_password() and WooCommerce's account implementation both fire
lostpassword_post with WP_Error and WP_User|false, so their valid-account
requests share the rate limits. A custom form is covered only if its execution
path fires that hook with the expected objects, normally by calling the
canonical reset flow. Direct calls to get_password_reset_key() or custom mail
code bypass it.
Proof versus rate-limit coverage
The proof token and honeypot are enforced only when $GLOBALS['pagenow'] is
wp-login.php, because only lostpassword_form receives the fields. The
WooCommerce form, custom templates, AJAX, and REST requests receive rate-limit
protection but no LW proof check.
Do not copy the private field constants or call private proof_ok() as an
integration API. Use lw-firewall-custom-form-adapter if the custom UI needs a
token/honeypot layer, and record that this is companion-owned behavior rather
than automatic reset-guard coverage.
Three counters
ResetLimiter::record() checks and increments in this order:
| Axis | Defaults | Key | Meaning |
|---|---|---|---|
| IP | 5 per 900 seconds | reset_ip_<ip> |
one requester |
| Global | 30 per hour | reset_all |
all attempts that reach this axis, including some later-refused attempts |
| Target account | 3 per 3600 seconds | reset_user_<user-id> |
one known account |
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.
- yesterday Changed · -2 lines fa09818beb2a
- 9d ago First seen · 194 lines · 123 tokens per session scan A 2b6d37dec752
lw-firewall-password-reset-protection is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 123 tokens to every session and 2,091 once invoked, about $0.0006 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
astro-seo
Audits and improves SEO for Astro sites. Use when the user asks to audit, set up, or improve SEO on an Astro site, or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema endpoints, NLWeb, hreflang, or search engine indexing in an Astro project. Produces drop-in code routed…
static-seo
Audits and improves SEO for static HTML sites. Use when the user asks to audit, set up, or improve SEO on a static site (Hugo, Jekyll, 11ty, Gatsby, Next.js static export, hand-rolled HTML, or wp-static-clone output), or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema…
readability-check
Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language. Checks ten categories — overall structure and topic order, paragraph structure, opening paragraph strength, tiered sentence length, passive voice, difficult words, filler and…
content-seo
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness and originality, content freshness, and internal linking. Use when the user asks "will this rank", "SEO check this post"…
wp-static-clone
Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx). Use when the user wants to "scrape", "freeze", "archive", "static-ify", or "move to [host]" a WordPress site, or asks to turn a sitemap into…
metadata-check
Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy, and other metadata where Flesch and paragraph-level readability checks don't apply. Checks front-loading, concreteness, filler, active voice…