add-plugin

Create and register AgentPay SDK plugins in src/plugins with CLI tests.

509|22|Updated Mar 17, 2026

Search Tags:#testing #architecture #integration #cli #plugin #agentpay

Ready to run

npx skills add https://github.com/worldliberty/agentpay-sdk --skill add-plugin-worldliberty

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-plugin
Source: https://github.com/worldliberty/agentpay-sdk/tree/main/skills/add-plugin
Command: npx skills add https://github.com/worldliberty/agentpay-sdk --skill add-plugin-worldliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines plugin onboarding by providing a standardized pattern to add, refactor, or generalize agentpay plugins, ensuring consistent wiring, testing, and registration.

Core Features & Use Cases

Create a new plugin module under src/plugins following the existing Bitrefill pattern.
Register the plugin in src/plugins/index.ts to become available in the CLI and daemon flows.
House plugin-specific API and scraping code under src/lib/<plugin> or src/lib/<plugin>/, while reusing the existing signing, policy, and broadcast pathways through CliPluginContext.
Add focused CLI tests under test/ to validate command integration and error handling.

Quick Start

Create a new plugin module following the established pattern and register it in the plugin registry.

Frequently Asked Questions about add-plugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add a new plugin to the AgentPay SDK?▼

To add a new plugin to the AgentPay SDK, create a plugin module under src/plugins, house its API code under src/lib/<plugin>, and register it in src/plugins/index.ts to wire it into the CLI and daemon flows.

What is the standard file structure for AgentPay plugin integration?▼

AgentPay plugin integration requires a plugin file under src/plugins, a plugin client under src/lib/<plugin>, and test scaffolding under test/ to validate command integration and error handling.

Do I need to register a plugin in src/plugins/index.ts for the CLI to recognize it?▼

Yes, you must register the plugin in src/plugins/index.ts to wire it into the CLI and daemon flows, making it available for use across commands while preserving signing and policy pathways.

How does CliPluginContext handle signing and policy for new plugins?▼

CliPluginContext allows new plugins to reuse the existing signing, policy, and broadcast pathways, ensuring that custom plugin API and scraping code under src/lib/<plugin> integrates consistently without breaking core flows.

Can I refactor an existing AgentPay plugin without breaking CLI commands?▼

Yes, you can refactor an existing plugin by following the standardized development pattern, keeping plugin-specific code under src/lib/<plugin>, and adding focused CLI tests under test/ to validate command integration and error handling.

What testing scaffolding is required when onboarding an AgentPay plugin?▼

Onboarding an AgentPay plugin requires adding focused CLI tests under test/ to validate command integration and error handling, ensuring the new plugin module works correctly within the CLI and daemon flows.