Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ASGCompute/asgcard-public --skill skillgit clone --depth 1 https://github.com/ASGCompute/asgcard-publicWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/asgcompute/asgcard-public/skill)<a href="https://agentmods.dev/skills/asgcompute/asgcard-public/skill"><img src="https://agentmods.dev/badge/skills/asgcompute/asgcard-public/skill.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.02226 |
| Opus 5 | $0.00010 | $0.01113 |
| Sonnet 5 | $0.00004 | $0.00445 |
| Haiku 4.5 | $0.00002 | $0.00223 |
Grade A, and why
asgcard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASG Card Agent Skill
CRITICAL: Always use
npx -y @asgcard/cli@latest(with@latesttag!) to ensure you are running the newest published version with all bug fixes.
⚠️ MANDATORY DATA RULES
NEVER use placeholder, test, or example data for email, phone, or name. You MUST ask the user for their real email address, phone number, and name before running any card creation or payment request command. If the user has previously provided their email/phone in the current conversation, you may reuse it. Otherwise, always ask first.
❌ WRONG:
-e "[email protected]" -p "+12345678900" -n "Test User"✅ RIGHT: Ask the user: "What email, phone number, and name should I use for the card?"
Onboarding (First Time)
Run the full 9-step onboarding wizard:
npx -y @asgcard/cli@latest onboard -y
Steps: Agent Skill → MCP Config → Wallet → API Registration → Telegram Identity → Wallet Activation → Fund Link → Balance Check → Summary
Canonical Flow (x402 / On-Chain USDC)
- Onboard: Run
asgcard onboard -yto set up wallet, MCP, and skill - Check wallet status: Use
get_wallet_statusMCP tool to verify wallet address and USDC balance - Fund wallet: Use
asgcard fund-linkor MCPget_fund_linkto generate a deposit URL - Check pricing: Use
get_pricingto see card and top-up pricing - Create a card: Use
create_cardwith amount, name, email, and phone — all provided by the user - Manage cards: Use
list_cards,get_card,get_card_details,freeze_card,unfreeze_card - Top up cards: Use
fund_cardto add funds to an existing card - Monitor: Use
get_transactionsandget_balanceto track activity
Stripe MPP Flow (Fiat Payments via Stripe)
Use this flow when the user wants to pay with a regular credit/debit card instead of USDC.
Step 1 — Create a Stripe Session (one-time setup)
npx -y @asgcard/cli@latest stripe:session <USER_EMAIL>
The user's real email is required. This creates a session saved to ~/.asgcard/stripe-session.json.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 240 lines · 21 tokens per session scan A d5b17eecc4be
asgcard is a skill published in the GitHub repository ASGCompute/asgcard-public (15 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 2,226 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
x402-stellar-payments
Use when asked to "pay for" a URL, add a "paid endpoint", handle HTTP 402, or work with x402 payments on Stellar.
t2000-job
Escrow USDC for agent-to-agent deliverable work (A2A jobs). Use when hiring another agent for async work (research reports, builds, SLA tasks) or when selling deliverable work yourself (list a service: fixed price + SLA, no server needed), or posting/claiming open jobs on the board (t2 job open / claim) — anything…
t2000-receive
Generate a payment request for the t2000 Agent Wallet — print the wallet address, an ANSI QR code, and (via MCP) a Payment Kit URI (sui:pay?…). Use when asked to receive a payment, share a wallet address, create a payment link, or set up a fund-me link.
t2000-send
Send USDC, USDsui, or SUI from the t2000 Agent Wallet to another Sui address. Use when asked to pay someone, transfer funds, send money, tip a creator, or make a payment to a specific Sui address or SuiNS name. Do NOT use for API payments — use the t2000-pay skill for x402-protected services.
t2000-swap
Swap tokens on Sui via Cetus Aggregator (20+ DEXs, best-route across SUI, USDC, USDsui, USDT, USDe, ETH, GOLD, NAVX, WAL, vSUI, and more). Use when asked to swap, trade, convert, exchange, or "turn X into Y". Do not use for sending — use the t2000-send skill for transfers.
okx-agent-payments-protocol
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channelid, opening / closing / topping up / settling / refunding a…