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 wedabro/bro-skills --skill speckit.wordpressgit clone --depth 1 https://github.com/wedabro/bro-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/wedabro/bro-skills/speckit.wordpress)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.wordpress"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.wordpress/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/wedabro/bro-skills/speckit.wordpress"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.wordpress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.01416 |
| Opus 5.5 | $0.00019 | $0.00566 |
| Sonnet 5.5 | $0.00009 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
speckit.wordpress 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Build industrial-grade, secure, performant, and highly interactive WordPress products (Themes, Plugins, Blocks), strictly adhering to official core developer guidelines, Spec-Driven Development, and modern WordPress 6.x standards.
Inputs and Outputs
- Read project requirements, theme/plugin source files,
theme.json,block.json, and Docker WordPress environment. - Produce core-compliant themes, blocks, plugins, REST routes, WP-CLI scripts, and performance-optimized queries.
Protocol
1. Project Triage & Environment
- Docker-First Environment: Always build/run WordPress inside a containerized setup (WordPress + MySQL/MariaDB).
- Core Triage: Detect project type (theme vs. plugin vs. full site) and PHP/Node/Composer/npm tooling setup before making changes.
- Theme Pathing: Place theme code under
wp-content/themes/[theme-slug]/. - Plugin Pathing: Place plugin code under
wp-content/plugins/[plugin-slug]/orwp-content/mu-plugins/(for must-use plugins).
2. Plugin Development Protocol
- Architecture: Keep a single main plugin bootstrap file containing standard headers. Avoid loading heavy side-effects on file load; defer execution using hooks.
- Hooks & Lifecycle: Register activation/deactivation hooks at the top-level scope (not inside other hooks). Implement safe uninstallation using
uninstall.phporregister_uninstall_hook. - Admin UI & Settings: Prefer the official Settings API (
register_setting,add_settings_section,add_settings_field) with propersanitize_callbackfor options storage.
3. Block (Gutenberg) Development Protocol
- Metadata-Driven: Define blocks using
block.jsonwithapiVersion: 3(WordPress 6.9+ standard) to ensure correct block iframe behavior. - Edit/Save/Render Patterns:
- In the Editor: Wrap component markup with
useBlockProps(). - Static blocks (markup saved in database): Use
useBlockProps.save()insave(). - Dynamic blocks (server-rendered): Set
"render": "file:./render.php"inblock.json(or use PHPrender_callback) and keepsave()returningnull. Useget_block_wrapper_attributes()in PHP.
- In the Editor: Wrap component markup with
- Block Composition: Use
useInnerBlocksProps()for container-like blocks. - Deprecations & Migrations: If modifying saved markup/attributes, add a
deprecatedarray (newest to oldest) in the client script to avoid "Invalid block" errors.
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.
- 1mo ago Changed · +4 lines 1386bd39fdb4
- 2mo ago First seen · 71 lines · 47 tokens per session scan A 2354f60ccb80
speckit.wordpress is a skill published in the GitHub repository wedabro/bro-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 47 tokens to every session and 1,416 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other skills, from other repositories
mx-lookup-post-batch
Retrieve MX records for up to 50 domains in a single request. Results for each domain are sorted by priority ascending (lowest numeric value has the highest mail delivery priority per RFC 5321).
email-validate-post-email
Validates a single email address and returns a full breakdown of syntax validity, MX record status, disposable domain check, normalized form, and any typo suggestion.
unit-conversion-post-batch
Skill "unit-conversion-post-batch" from bobadilla-tech/requiems-api-skills, covering endpoint, batch convert units, parameters, request example and response example.
domain-info-get-{domain}
Returns DNS records and availability status for the given domain.
email-normalize-post-normalize
Normalizes a single email address and returns the canonical form together with a breakdown of all transformations applied.
geocode-get-reverse-geocode
Converts geographic coordinates into a human-readable address.