What is bd-companion-plugin?

A companion WordPress plugin used as a live integration testbed for the better-data library. Integration tests check behavior that unit tests without WordPress cannot reach.

It is for smoke, stress, and integration testing of caching, metadata, REST schemas, locale changes, encryption settings, and related WordPress behavior.

It keeps fast, WordPress-free unit tests separate from tests that need a real WordPress installation, database, REST API, or locale.

bd-companion-plugin — Skill for Claude Code and Codex by Lonsdale201

Install

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.

Any agent

npx skills add Lonsdale201/wp-agent-skills --skill bd-companion-plugin

Clone the repo

git clone --depth 1 https://github.com/Lonsdale201/wp-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/bd-companion-plugin/github.svg)](https://agentmods.dev/skills/lonsdale201/wp-agent-skills/bd-companion-plugin)

Your own site

<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/bd-companion-plugin"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/bd-companion-plugin/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/bd-companion-plugin"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/bd-companion-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 220 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,439 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00220	$0.03439
Opus 5.5	$0.00088	$0.01376
Sonnet 5.5	$0.00044	$0.00688
Haiku 4.5	$0.00022	$0.00344

Measured 2mo ago against content hash ba817c2320ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bd-companion-plugin 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 2mo 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.

better-data/bd-companion-plugin/SKILL.md · 309 lines

How it starts

The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.

better-data: Companion plugin testbed

For library maintainers working in the integration testbed at wp-content/plugins/better-data-plugin-test/. The plugin's job is to verify better-data behavior against real WordPress — things that pure unit tests can't reach (cache primings, metadata_exists semantics, wp_slash round-trips, REST schema actually appearing in WP_REST_Server, locale switching, encryption key constants).

Misconception this skill corrects

"I'll add the new feature's integration test directly inside better-data/tests/Unit/ so everything's in one place."

Wrong. tests/Unit/ is the WP-free zone — every test there must run with composer test against a clean PHP environment, no WP bootstrap, no MySQL. That's intentional: contributors can run the unit suite in seconds. WP-aware behavior goes in the companion plugin, where there's a real WordPress to talk to.

The split:

Concern	Lives in
Pure type coercion, attribute reflection, builder logic	`better-data/tests/Unit/`
`wp_slash` round-trip, `metadata_exists` semantics, REST registration	`better-data-plugin-test/src/Smoke/`
Multi-step scenarios (encrypt → store → fetch → decrypt → reveal), edge-case discovery	`better-data-plugin-test/src/Stress/`
Visual confirmation (admin page renders `print_r($dto)`)	`better-data-plugin-test/src/Admin/`

Other AI-prone misconceptions:

"I'll let the plugin depend on WooCommerce since it makes the Order fixture realistic." Wrong — the plugin must run on a clean WP install with NOTHING but better-data. WC, ACF, custom-fields plugins are out. The Widget Shop fixture (bd_widget CPT + bd_order CPT + ShopSettingsDto) IS the realistic consumer because it's self-contained.
"If a stress scenario is flaky, I'll mark it as NOTE instead of fixing it." Wrong — NOTE is for documented quirks the library legitimately surfaces (e.g. "WP serializes integer-keyed arrays as objects in some contexts"). A flaky test is a FAIL waiting to happen; fix it.
"I'll move the new behavior into the library after the plugin verifies it." Wrong direction — integration-only behavior STAYS in the plugin. The library stays shape-agnostic.

Read the full file on GitHub · 309 lines

Changes

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.

2mo ago First seen · 309 lines · 220 tokens per session scan A ba817c2320ab

Subscribe to this mod's changes

bd-companion-plugin is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (26 stars, last pushed 17d ago), licensed MIT. It adds 220 tokens to every session and 3,439 once invoked, about $0.0009 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-30.

E2E testing Testing agent-skills skills wordpress

bd-companion-plugin next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
bd-companion-pluginLonsdale201/wp-agent-skills	Skill	26	17d ago	MIT	A	220	Claude Code, Codex
testing-blocksadobe/skills	Skill	319	today	Apache-2.0	A	61	Claude Code
appbuilder-e2e-testingadobe/skills	Skill	319	today	Apache-2.0	A	144	Claude Code
accessibility-testing-expertroedyrustam/vibes-plug	Skill	122	today	MIT	A	45	Cursor
qa-systematicMathews-Tom/armory	Skill	341	today	MIT	A	62	Claude Code
test-slack-appslackapi/slack-skills-plugin	Skill	165	today	MIT	A	111	Claude Code
dogfoodAtlasOmnia/donna-starter	Skill	138	11d ago	MIT	A	20	Claude Code, Codex