agentleFS
SumitShinde0702SumitShinde0702/aipaysdk/skills/agentpay-sdk/agents/AGENTS.md

aipaysdk / agents

AGENTS.md2 starsChanged 4 months agoMITView on GitHub

Use the installed agentpay-sdk skill whenever the task touches Link fiat setup, wallet setup, funding, policy, transfers, approvals, cards, or backups. Rules that must stay consistent:

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository5 other files it gives its agents.

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

15 rules. About 1 is common, 2 are distinctive, and 12 are very specific to this project.

  • ≈1

    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
  1. Very specific:

    Use the installed agentpay-sdk skill whenever the task touches Link fiat setup, wallet setup, funding, policy, transfers, approvals, cards, …

    line 3
  2. Very specific:

    create one-time card credentials with agentpay link card --payment-method-id <id> --merchant-name <name> --merchant-url <url> --amount …

    line 10
  3. Very specific:

    use agentpay wallet --json to decide whether a reusable wallet already exists

    line 12
  4. Very specific:

    if the user only asks what the skill can do, answer from SKILL.md and do not probe the machine first

    line 13
  5. Very specific:

    never ask the user to paste VAULT_PASSWORD into chat

    line 14
  6. Common:

    never ask the user to paste Link card numbers, CVCs, access tokens, refresh tokens, or full credential files into chat

    line 15
  7. Very specific:

    if wallet metadata is unavailable on macOS/Linux, tell them to run agentpay admin setup locally.

    line 16
  8. Very specific:

    if the wallet exists and the user wants to preserve it while re-running setup, tell them to run agentpay admin setup …

    line 17
  9. Very specific:

    after a fresh setup, tell the user to create an encrypted offline backup with agentpay admin wallet-backup export --output <PATH> unless …

    line 18
  10. Very specific:

    if the local wallet is gone but the user has an encrypted backup, tell them to run agentpay admin setup --restore-wallet-from <PATH> locally

    line 19
  11. Very specific:

    if the user does not specify network or asset for a payment, default to USD1 on bsc (on aipay:local, prefer the active chain)

    line 20
  12. Distinctive:

    check funding before outbound actions

    line 21
  13. Distinctive:

    if funding is missing, stop and ask the user to fund the wallet with the exact address, network, token needs, and BNB gas needs

    line 22
  14. Very specific:

    use agentpay --help / pnpm aipay:local --help as the source of truth for exact flags

    line 24
  15. Very specific:

    use agentpay admin tui as the default path for daemon policy.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AiPay SDK Adapter

Use the installed agentpay-sdk skill whenever the task touches Link fiat setup, wallet setup, funding, policy, transfers, approvals, cards, or backups.

Rules that must stay consistent:

  • start from agentpay config show --json
  • for fiat/card payments, start with agentpay link status --json; if Link is not authenticated, use agentpay link onboard
  • list Link payment methods with agentpay link payment-methods --json
  • create one-time card credentials with agentpay link card --payment-method-id <id> --merchant-name <name> --merchant-url <url> --amount <cents> --context <100+ char explanation> --output-file <PATH> and never print full card details into chat
  • for third-party program integration, use @aipaysdk/sdk/link helpers through the AiPay Link facade
  • use agentpay wallet --json to decide whether a reusable wallet already exists
  • if the user only asks what the skill can do, answer from SKILL.md and do not probe the machine first
  • never ask the user to paste VAULT_PASSWORD into chat
  • never ask the user to paste Link card numbers, CVCs, access tokens, refresh tokens, or full credential files into chat
  • if wallet metadata is unavailable on macOS/Linux, tell them to run agentpay admin setup locally; on Windows / monorepo use pnpm aipay:local setup (dashboard optional)
  • if the wallet exists and the user wants to preserve it while re-running setup, tell them to run agentpay admin setup --reuse-existing-wallet locally
  • 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 local wallet is gone but the user has an encrypted backup, tell them to run agentpay admin setup --restore-wallet-from <PATH> locally
  • if the user does not specify network or asset for a payment, default to USD1 on bsc (on aipay:local, prefer the active chain)
  • 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
  • if a request hits manual approval, say it is waiting for the user's approval and use local admin CLI approval commands first; for transfer --broadcast, transfer-native --broadcast, approve --broadcast, and bitrefill buy --broadcast, tell them to keep the original command running and not rerun it after approval; if that original broadcast command is already gone after approval, use agentpay admin resume-manual-approval-request --approval-request-id <UUID>
  • use agentpay --help / pnpm aipay:local --help as the source of truth for exact flags
  • use agentpay admin tui as the default path for daemon policy; on aipay:local use pnpm aipay:local rules

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.