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-feed-integrationgit 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-feed-integration)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/fluentform-feed-integration"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentform-feed-integration/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-feed-integration"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/fluentform-feed-integration.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.00121 | $0.02022 |
| Opus 5 | $0.00060 | $0.01011 |
| Sonnet 5 | $0.00024 | $0.00404 |
| Haiku 4.5 | $0.00012 | $0.00202 |
Grade A, and why
fluentform-feed-integration 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fluent Forms feed integrations
Use the Free-core feed manager when administrators need credentials, reusable
per-form feeds, field mapping, conditions, logs, and background delivery. Use a
plain submission_inserted listener only for small, non-configurable local work.
Read integration-contract.md before implementing the manager class or deciding retry/idempotency behavior.
Availability contract
FluentForm\App\Http\Controllers\IntegrationManagerController, feed metadata,
the notification manager, ff_scheduled_actions, and bundled Action Scheduler
are Free-core surfaces in 6.2.7. Mailchimp is a Free reference implementation.
Many shipped connectors under fluentformpro/src/Integrations are Pro-only, but
their existence does not make a third-party integration manager require Pro.
Use the current controller directly. These aliases are deprecated in 6.2.7:
FluentForm\App\Services\Integrations\IntegrationManagerFluentForm\App\Services\Integrations\BaseIntegration
Decision point
Use a feed manager when at least one applies:
- admins create multiple destinations or mappings per form;
- delivery has form conditions or smart codes;
- credentials need a global connection screen;
- delivery should run asynchronously and appear in integration logs;
- a failed/replayed request needs an idempotency contract.
Use a direct hook for bounded local metadata/state changes with no settings UI. Do not build a feed abstraction around a single pure calculation.
Registration workflow
- Bootstrap once on
fluentform/loaded; require the controller class. - Choose three stable identifiers:
- integration key for addon/global UI;
- namespaced option key for connection settings;
- feed settings key stored in
fluentform_form_metaand used in the dynamic notification hook.
- Extend
IntegrationManagerController, call the parent constructor, set the description/logo/category, then callregisterAdminHooks(). - Implement global settings and verify credentials server-side before setting
status => true. - Implement integration availability, feed defaults, settings fields, and merge
fields. Keep
enabledandconditionalsin the feed schema. - Implement
notify($feed, $formData, $entry, $form)as an idempotent operation. - Report every terminal result through
fluentform/integration_action_result. - Test disabled, unconfigured, condition-false, sync, async, timeout, retry, and duplicate delivery paths.
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.
- yesterday Changed · -1 lines bfecb020c81b
- 9d ago First seen · 225 lines · 121 tokens per session scan A 305730904a44
fluentform-feed-integration is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 121 tokens to every session and 2,022 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.