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 fluentform-submission-lifecyclegit 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/fluentform-submission-lifecycle)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/fluentform-submission-lifecycle"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentform-submission-lifecycle/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/fluentform-submission-lifecycle"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentform-submission-lifecycle.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.00120 | $0.01826 |
| Opus 5 | $0.00060 | $0.00913 |
| Sonnet 5 | $0.00024 | $0.00365 |
| Haiku 4.5 | $0.00012 | $0.00183 |
Grade A, and why
fluentform-submission-lifecycle 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fluent Forms submission lifecycle
Choose hooks from the actual server-side order. Browser data is untrusted, and an action that sounds “before insert” is not a replacement for validation.
Read hook-order.md before changing stored values, adding a remote side effect, handling payment forms, or reacting to Pro drafts.
Canonical lifecycle
raw serialized request
-> form field parsing and accepted-key allowlist
-> recursive Fluent Forms sanitization
-> restrictions / CAPTCHA / input normalization / validation
-> spam checks
-> response-data and insert-row filters
-> submission row insert
-> before-actions hook
-> entry-details projection
-> submission-inserted hooks and feeds
-> confirmation filters
Unknown request keys are removed before validation unless explicitly placed on
Fluent Forms' protocol-key allowlist. The accepted $formData is therefore not
the same object as raw $_POST or the controller's parsed input.
Hook selection
| Need | Use | Important timing |
|---|---|---|
| Normalize one element before rules | fluentform/input_data_{element} |
Before validator |
| Change rule/message definitions | fluentform/validations |
Before validator |
| Add cross-field errors | fluentform/validation_errors |
Before rejection/insert |
| Change accepted response data | fluentform/insert_response_data |
After validation, before JSON encode |
| Change DB row columns | fluentform/filter_insert_data |
Low-level, immediately before insert |
| Observe imminent insert | fluentform/before_insert_submission |
Action, after validation; cannot return changed data |
| React to a durable entry | fluentform/submission_inserted |
Row and entry details exist |
| Change browser confirmation | fluentform/submission_confirmation |
Last response stage |
Do not use fluentform/before_insert_submission for normal validation. In 6.2.7
it is an action after handleValidation() and receives $insertData by value.
Use validation filters so the browser gets field-shaped errors and no row is
created.
What ships with it
2 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.
- 9d ago First seen · 205 lines · 120 tokens per session scan A 8e33f488c175
fluentform-submission-lifecycle is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 120 tokens to every session and 1,826 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
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.