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 wp-connectors-apigit 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/wp-connectors-api)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/wp-connectors-api"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wp-connectors-api/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/wp-connectors-api"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/wp-connectors-api.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.00123 | $0.02479 |
| Opus 5 | $0.00062 | $0.01239 |
| Sonnet 5 | $0.00025 | $0.00496 |
| Haiku 4.5 | $0.00012 | $0.00248 |
Grade A, and why
wp-connectors-api 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 2d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Connectors API
WordPress 7.0 introduced the Connectors API; 7.1 adds Application Password credentials. Core uses the registry for Settings > Connectors and AI provider credentials. A connector is not the service client itself: it describes how the service is named, displayed, installed, authenticated, and discovered.
When to use this skill
Trigger when ANY of the following is true:
- Code calls
wp_get_connector(),wp_get_connectors(),wp_is_connector_registered(), or hookswp_connectors_init. - A plugin needs to appear on Settings > Connectors or expose provider credentials.
- The task mentions WordPress connectors, AI provider setup, API keys, Application Password credentials,
WP_Connector_Registry, or@wordpress/connectors. - Reviewing code that stores API keys or
username/passwordcredential objects for an external service.
Availability
The Connectors API is core-only in WordPress 7.0+. Public lookup functions are available after init, because core initializes the registry on init priority 15. Feature-detect application_password support when retaining WordPress 7.0 compatibility.
AI provider connectors are registered only when wp_supports_ai() is true. wp_supports_ai() can be disabled by WP_AI_SUPPORT or the wp_supports_ai filter, so AI connectors must be feature-detected.
Public lookup API
Use these outside the wp_connectors_init callback:
if ( wp_is_connector_registered( 'openai' ) ) {
$connector = wp_get_connector( 'openai' );
}
foreach ( wp_get_connectors() as $id => $connector ) {
// $connector['name'], $connector['type'], $connector['authentication'].
}
Do not instantiate or replace WP_Connector_Registry directly.
Registering a connector
Register new connectors on wp_connectors_init. The callback receives the registry instance:
add_action( 'wp_connectors_init', static function ( WP_Connector_Registry $registry ): void {
$registry->register(
'my_service',
array(
'name' => __( 'My Service', 'myplugin' ),
'description' => __( 'Syncs content with My Service.', 'myplugin' ),
'type' => 'content_sync',
'authentication' => array(
'method' => 'api_key',
'credentials_url' => 'https://example.com/account/api-keys',
'setting_name' => 'myplugin_my_service_api_key',
'constant_name' => 'MYPLUGIN_MY_SERVICE_API_KEY',
'env_var_name' => 'MYPLUGIN_MY_SERVICE_API_KEY',
),
'plugin' => array(
'file' => 'myplugin/myplugin.php',
'is_active' => static fn (): bool => defined( 'MYPLUGIN_VERSION' ),
),
)
);
} );
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.
- 2d ago First seen · 233 lines · 123 tokens per session scan A 994a954ac6fa
wp-connectors-api is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 123 tokens to every session and 2,479 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-11.
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.