agentpay-sdk / agents
CLAUDE.md460 starsChanged 8 months agoMITView on GitHub
Use the installed agentpay-sdk skill whenever the task touches wallet setup, funding, spending limits, transfers, paid APIs, approvals, or backups. Rules that must stay consistent:
In this repository5 other files it gives its agents.
- skills/agentpay-sdk/agents/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/agentpay-sdk/agents/copilot-instructions.mdCopilot instructions
- add-pluginSkill
- agentpay-sdkSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
14 rules. About 0 are common, 2 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use the installed agentpay-sdk skill whenever the task touches wallet setup, funding, spending limits, transfers, paid APIs, approvals, or …
- Very specific: line 8
use agentpay wallet --json to decide whether a reusable wallet already exists.
- Very specific: line 9
if the user only asks what the skill can do, answer from SKILL.md and do not probe the machine first
- Distinctive: line 10
never ask the user to paste a wallet backup passphrase, agent auth token, or paying-proxy URL into chat.
- Very specific: line 11
never run sudo or agentpay admin decisions for the user.
- Very specific: line 12
if AgentPay is not set up and the user is trying to use the wallet, tell them to run agentpay setup locally
- Very specific: line 13
if the wallet exists and the user wants to preserve it while re-running setup, tell them to run agentpay setup locally and choose "Keep the …
- Very specific: line 14
if the local wallet is gone but the user has an encrypted backup, tell them to run agentpay setup locally and choose "Restore from a backup"
- Very specific: line 15
after a fresh setup, tell the user to create an encrypted offline backup with agentpay admin wallet-backup export --output <PATH> unless …
- Very specific: line 16
if the user does not specify network or asset for a payment, default to USD1 on bsc
- Distinctive: line 17
check funding before outbound actions
- Very specific: line 18
if funding is missing, stop and ask the user to fund the wallet with the exact address, network, token needs, and BNB gas needs (agentpay …
- Very specific: line 23
use agentpay --help and subcommand help as the source of truth for exact flags
- Very specific: line 24
use agentpay admin limits (run by the user) as the default path for spending limit changes
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AgentPay SDK Adapter
Use the installed agentpay-sdk skill whenever the task touches wallet setup, funding, spending limits, transfers, paid APIs, approvals, or backups.
Rules that must stay consistent:
- start from
agentpay config show --json - use
agentpay wallet --jsonto decide whether a reusable wallet already exists; exit code4means AgentPay is not set up for this user - if the user only asks what the skill can do, answer from
SKILL.mdand do not probe the machine first - never ask the user to paste a wallet backup passphrase, agent auth token, or paying-proxy URL into chat; there is no vault password
- never run
sudooragentpay admindecisions for the user; admin actions need the user's Touch ID, Mac password, or sudo, so give them the exact command to run locally - if AgentPay is not set up and the user is trying to use the wallet, tell them to run
agentpay setuplocally - if the wallet exists and the user wants to preserve it while re-running setup, tell them to run
agentpay setuplocally and choose "Keep the existing wallet" - if the local wallet is gone but the user has an encrypted backup, tell them to run
agentpay setuplocally and choose "Restore from a backup" - after a fresh setup, tell the user to create an encrypted offline backup with
agentpay admin wallet-backup export --output <PATH>unless they already have a verified backup - if the user does not specify network or asset for a payment, default to
USD1onbsc - check funding before outbound actions
- if funding is missing, stop and ask the user to fund the wallet with the exact address, network, token needs, and BNB gas needs (
agentpay fund --json) - pass
--jsonand read exit codes:0ok,1failure (followerror.next_action),2usage,3waiting for manual approval,4not set up - amounts for
transfer,transfer-native,approve, and the Solana transfers are decimal whole units; amounts forx402andmppare integer base units - if a request hits manual approval, say it is waiting for the user's approval and give them
agentpay admin approve <UUID>; for EVM and Solana--broadcastpayments, tell them to keep the original command running and not rerun it; if that command already exited with code3, useagentpay resume --approval-request-id <UUID>after approval - Stripe Link, Bitrefill, and private transfers are not available
- use
agentpay --helpand subcommand help as the source of truth for exact flags - use
agentpay admin limits(run by the user) as the default path for spending limit changes
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.

