add-plugin
Skill2 starsChanged 4 months agoMITView on GitHub
Use this skill when the user wants to add, refactor, or generalize a `agentpay <plugin>` integration like Bitrefill. Follow the shared plugin registration path under `src/plugins`, keep plugin-specific API or scraping code under `src/lib/<plugin>` or `src/lib/<plugin>/`, reuse the existing Rust daemon signing and policy path through the shared CLI plugin context instead of reimplementing signing, and add focused CLI tests for the new plugin.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- github/plugin-marketplace-startertheir own version, first seen Nov 15, 2026
- cTuningLabs/cmetatheir own version, first seen Nov 8, 2026
- worldliberty/agentpay-sdktheir own version, first seen Nov 1, 2026
- fastrepl/anarlogtheir own version, first seen Oct 8, 2026
- fastrepl/hyprnotetheir own version, first seen Oct 8, 2026
- odere-pro/claude-software-3-0-marketplacetheir own version, first seen Jun 5, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- fastrepl/anarlog★ 9.9ksame name
- fastrepl/hyprnote★ 9.9ksame name
- worldliberty/agentpay-sdk★ 460same name
- cTuningLabs/cmeta★ 9same name
- github/plugin-marketplace-starter★ 7same name
- PierrickMartos/Leadership-Skills★ 4same name
- odere-pro/claude-software-3-0-marketplace★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- skills/agentpay-sdk/agents/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/agentpay-sdk/agents/CLAUDE.mdCLAUDE.md
- skills/agentpay-sdk/agents/copilot-instructions.mdCopilot instructions
- agentpay-sdkSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 5 are distinctive, and 15 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the task is "add another plugin like Bitrefill" or "make plugin onboarding more reusable."
- Very specific: line 23
Keep plugin-local API normalization, transports, cookies, scraping, or challenge handling in src/lib/<plugin>*.
- Very specific: line 24
Keep src/cli.ts responsible only for assembling shared dependencies and calling registerBuiltinCliPlugins(...).
- Very specific: line 29
Do not add another large inline .command('<plugin>') block to src/cli.ts.
- Distinctive: line 30
Do not reimplement signing, nonce management, or policy logic in the plugin.
- Very specific: line 31
If the plugin needs onchain payment, default to preview-first behavior and make live payment explicit with --broadcast.
- Very specific: line 32
If the plugin only needs a quote plus an optional live payment path, prefer one buy-style command over a redundant separate price command.
- Distinctive: line 33
Keep plugin-specific error handling inside the plugin module when possible.
- Distinctive: line 34
If a remote API needs browser bootstrap, Cloudflare handling, or cookies, isolate that behind the plugin's transport/client layer instead …
- Very specific: line 40
Add or extend the plugin client under src/lib/<plugin>*.
- Very specific: line 41
Add a new CliPlugin implementation under src/plugins/<plugin>.ts.
- Very specific: line 43
If the plugin needs signing or broadcast, use context.config, context.agent, and context.broadcast instead of shelling around the shared …
- Very specific: line 44
Add a focused CLI test file or extend the closest existing one under test/.
- Very specific: line 45
Run the plugin-focused tests and at least one agentpay <plugin> --help smoke check.
- Distinctive: line 49
Prefer mocked CLI/integration tests over live third-party dependencies.
- Very specific: line 51
If the plugin supports --broadcast, cover both preview-only and broadcast-backed flows.
- Very specific: line 55
Read src/plugins/types.ts for the shared context contract.
- Very specific: line 56
Read src/plugins/index.ts for plugin registration.
- Very specific: line 57
Read src/plugins/bitrefill.ts for the current plugin pattern.
- Very specific: line 58
Read the matching src/lib/<plugin>* module only when implementing that plugin's remote API behavior.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Plugin
Use this skill when the task is "add another plugin like Bitrefill" or "make plugin onboarding more reusable."
Ground Truth
src/cli.tsis the main CLI entrypoint, but plugin-specific command trees should not be wired inline there.src/plugins/types.tsdefines the sharedCliPluginContextand the generic plugin registrar shape.src/plugins/index.tsis the registry for built-in plugins.src/plugins/bitrefill.tsis the reference implementation for a plugin that owns its own command tree.- Plugin-specific HTTP or browser/bootstrap code belongs in
src/lib/<plugin>.tsorsrc/lib/<plugin>/. - Signing, policy checks, manual approval handling, and raw transaction broadcast plumbing stay on the existing AgentPay path exposed through
CliPluginContext.
Default Architecture
- Create
src/plugins/<plugin>.ts. - Register the plugin in
src/plugins/index.ts. - Keep plugin-local API normalization, transports, cookies, scraping, or challenge handling in
src/lib/<plugin>*. - Keep
src/cli.tsresponsible only for assembling shared dependencies and callingregisterBuiltinCliPlugins(...). - Reuse
context.agent.runJson(...)pluscontext.broadcast.*for any payment flow that reaches the daemon.
Implementation Rules
- Do not add another large inline
.command('<plugin>')block tosrc/cli.ts. - Do not reimplement signing, nonce management, or policy logic in the plugin.
- If the plugin needs onchain payment, default to preview-first behavior and make live payment explicit with
--broadcast. - If the plugin only needs a quote plus an optional live payment path, prefer one
buy-style command over a redundant separatepricecommand. - Keep plugin-specific error handling inside the plugin module when possible.
- If a remote API needs browser bootstrap, Cloudflare handling, or cookies, isolate that behind the plugin's transport/client layer instead of leaking it into the shared CLI.
- Pass only shared helpers through
CliPluginContext; keep plugin business logic inside the plugin module.
Deterministic Workflow
- Inspect
src/plugins/bitrefill.tsto copy the current plugin structure and command style. - Add or extend the plugin client under
src/lib/<plugin>*. - Add a new
CliPluginimplementation undersrc/plugins/<plugin>.ts. - Register it in
src/plugins/index.ts. - If the plugin needs signing or broadcast, use
context.config,context.agent, andcontext.broadcastinstead of shelling around the shared flow. - Add a focused CLI test file or extend the closest existing one under
test/. - Run the plugin-focused tests and at least one
agentpay <plugin> --helpsmoke check.
Testing Rule
- Prefer mocked CLI/integration tests over live third-party dependencies.
- Cover command registration, happy path output, unsupported modes, and any explicit challenge or approval state.
- If the plugin supports
--broadcast, cover both preview-only and broadcast-backed flows.
References
- Read
src/plugins/types.tsfor the shared context contract. - Read
src/plugins/index.tsfor plugin registration. - Read
src/plugins/bitrefill.tsfor the current plugin pattern. - Read the matching
src/lib/<plugin>*module only when implementing that plugin's remote API behavior.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

