Add or refactor agentpay plugins into the shared CLI/daemon architecture.
npx skills add https://github.com/cwsqwe123/RamCoin --skill add-plugin-cwsqwe123
Please help me install this Agent Skill. Skill: add-plugin Source: https://github.com/cwsqwe123/RamCoin/tree/main/skills/add-plugin Command: npx skills add https://github.com/cwsqwe123/RamCoin --skill add-plugin-cwsqwe123
This Skill reduces the friction of adding or refactoring agentpay integrations by giving a reusable, consistent path for wiring a new plugin into the existing CLI/daemon flow.
src/plugins/<plugin>.ts, register it in src/plugins/index.ts, and keep plugin business logic isolated.CliPluginContext for signing, policy checks, approvals, and transaction broadcast rather than duplicating core wallet plumbing.src/lib/<plugin>* so shared CLI code stays clean.--help, happy paths, unsupported modes, and --broadcast preview vs live behavior.src/plugins/bitrefill.ts as the canonical example of command style and plugin boundaries.Ask the AI to help you add a new agentpay <plugin> integration by following the shared plugin registration pattern in src/plugins, placing plugin-specific API or scraping code in src/lib/<plugin>, reusing CliPluginContext for signing and policy, and adding focused CLI tests for the new command tree.
High-intent search queries and answers about installing and using this skill.
To add a new payment provider plugin, create a dedicated `src/plugins/<plugin>.ts` file, register it in `src/plugins/index.ts`, and isolate HTTP or scraping logic under `src/lib/<plugin>*` to maintain a clean CLI daemon architecture.
The best way to structure transaction signing and policy checks is to reuse the shared `CliPluginContext` rather than duplicating core wallet plumbing, ensuring consistent approvals and transaction broadcasts across all CLI plugin integrations.
You should test CLI plugin commands using deterministic mocked CLI tests that specifically cover `--help` outputs, happy paths, unsupported modes, and the differences between `--broadcast` live behavior and preview executions.
Yes, agentpay plugin development requires isolating browser bootstrap behavior, scraping, cookies, and HTTP calls under `src/lib/<plugin>*` so the shared CLI code and daemon plugin architecture remain clean and maintainable.
You can refactor an existing payment integration by applying the shared plugin registration pattern, using `src/plugins/bitrefill.ts` as the canonical reference for command style, plugin boundaries, and consistent transport implementation.
CLI plugin integrations have inconsistent transaction broadcasts when core wallet plumbing is duplicated instead of reusing `CliPluginContext` for signing, policy checks, approvals, and broadcast flows across the daemon architecture.
worldlibertyCreate and register AgentPay SDK plugins in src/plugins with CLI tests.
mahg-esGenerate unit tests for functions, methods, and classes using the project's test framework.
ccfCodify Nx workspace patterns for monorepo setup, boundary enforcement, and caching.
qol-toolsManages PointZ desktop daemon lifecycle, UDP discovery, TCP transport, status API, and cross-platform input injection for qol-tray plugin development and debugging.