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 jfb-settings-tabgit 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/jfb-settings-tab)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/jfb-settings-tab"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/jfb-settings-tab/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/jfb-settings-tab"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/jfb-settings-tab.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.00147 | $0.04159 |
| Opus 5 | $0.00073 | $0.02080 |
| Sonnet 5 | $0.00029 | $0.00832 |
| Haiku 4.5 | $0.00015 | $0.00416 |
Grade A, and why
jfb-settings-tab 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JetFormBuilder: register a custom settings tab
JetFormBuilder ships with its own Vue-based admin Settings page. Companion plugins should not create separate add_options_page() screens — they should plug into the JFB Settings page as a tab. This skill describes the official API for doing so.
API stability note
The Base_Handler PHP API and the jet.fb.register.settings-page.tabs JS filter described here are stable across the entire JFB 3.x line and have not had breaking changes in the version range observed. The cx-vui-* Vue components are also stable. The plugin-version-tested field in the frontmatter records only the version where this skill was last verified end-to-end — treat it as "this skill was confirmed accurate on at least this version", not as "this is the only version where it works". Almost certainly this skill applies to JFB 3.0+ unchanged. If you encounter a JFB version where any step here is wrong, please file an issue and bump the field — don't silently work around it.
The flow has two halves that must both be implemented:
- PHP side — a
Base_Handlersubclass for persistence + thejet-form-builder/register-tabs-handlersfilter to register it. - JS side — a Vue component + the
jet.fb.register.settings-page.tabsJS filter (viawp.hooks.addFilter) to render it.
Skip either half and the tab silently won't appear or won't save.
When to use this skill
- A companion plugin needs a configuration tab inside JFB Settings.
- The user mentions API keys, OAuth, third-party integrations that need a settings UI for JFB.
- The diff/files contain
Base_Handler,register-tabs-handlers,jet.fb.register.settings-page.tabs,cx-vui-*, orPages_Manager.
Architecture in one paragraph
Tab_Handler_Manager (singleton) collects tab handlers via the jet-form-builder/register-tabs-handlers filter. Each handler is a Base_Handler subclass with a slug(), on_load() (returns saved options to Vue), and on_get_request() (saves POST data). On the JS side, the JFB admin bundle reads a Vue-side filter jet.fb.register.settings-page.tabs to collect tab components. Each component receives saved options as props.incoming and exposes a getRequestOnSave() method that returns { data: {...} }. JFB persists the data to wp_options under the key jet_form_builder_settings__<slug> as JSON, via an AJAX action wp_ajax_jet_fb_save_tab__<slug> with nonce jfb-settings and capability manage_options.
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 · 346 lines · 147 tokens per session scan A 14871bafb3b6
jfb-settings-tab is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 147 tokens to every session and 4,159 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
airflow-plugins
Builds Airflow 3.1+ plugins that embed FastAPI apps, custom UI pages, React components, middleware, macros, and operator links directly into the Airflow UI. Use when building anything custom inside Airflow 3.1+ that involves Python and a browser-facing interface - creating an Airflow plugin, adding a custom UI page or…
nextjs-app-router
Provides patterns and code examples for building Next.js 16+ applications with App Router architecture. Use when creating projects with App Router, implementing Server Components and Client Components ("use client"), creating Server Actions for forms, building Route Handlers (route.ts), configuring caching with "use…
nextjs-data-fetching
Provides Next.js App Router data fetching patterns including SWR and React Query integration, parallel data fetching, Incremental Static Regeneration (ISR), revalidation strategies, and error boundaries. Use when implementing data fetching in Next.js applications, choosing between server and client fetching, setting…
nextjs-patterns
Next.js best practices, server components, app router patterns, caching strategies, and full-stack architecture.
yida-canvas-data-binding
A method for connecting a YidaCodeCanvas page to real data from Yida forms, connectors, or same-site APIs. YidaCodeCanvas is the component used to run custom React pages inside Yida.
openyida
A skill for creating and changing applications on 宜搭 (Yida), a Chinese low-code platform for building business apps with less hand-written code. It first checks the available tools, login status, project folder, and target application before making changes.