Install the "agent-wallet-policy" agent skill from https://github.com/circlefin/skills/tree/master/plugins/circle/skills/agent-wallet-policy into .claude/skills/agent-wallet-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-wallet-policy", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add circlefin/skills --skill agent-wallet-policy -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "agent-wallet-policy" agent skill from https://github.com/circlefin/skills/tree/master/plugins/circle/skills/agent-wallet-policy into .agents/skills/agent-wallet-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-wallet-policy", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add circlefin/skills --skill agent-wallet-policy -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "agent-wallet-policy" agent skill from https://github.com/circlefin/skills/tree/master/plugins/circle/skills/agent-wallet-policy into .cursor/skills/agent-wallet-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-wallet-policy", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add circlefin/skills --skill agent-wallet-policy -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "agent-wallet-policy" agent skill from https://github.com/circlefin/skills/tree/master/plugins/circle/skills/agent-wallet-policy into .gemini/skills/agent-wallet-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-wallet-policy", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add circlefin/skills --skill agent-wallet-policy -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "agent-wallet-policy" agent skill from https://github.com/circlefin/skills/tree/master/plugins/circle/skills/agent-wallet-policy into .github/skills/agent-wallet-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-wallet-policy", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add circlefin/skills --skill agent-wallet-policy -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "agent-wallet-policy" agent skill from https://github.com/circlefin/skills/tree/master/plugins/circle/skills/agent-wallet-policy into .opencode/skills/agent-wallet-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-wallet-policy", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
agent-wallet-policy
GitHub stars
155
Token cost
~1.7k tokens
SKILL.md length
877 words
Files
2 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0
At a glance
View spending policy on a Circle agent wallet — per-transaction, daily, weekly, and monthly USDC caps via the circle CLI.
Works in 3 steps: Confirm values with the user → Hand the user the command → Verify after the user reports done
The user wants to inspect current limits
SKILL.md covers Overview, Prerequisites, Viewing current limits… and Setting or resetting limits…, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Agent Wallet Policy is an agent skill from circlefin/skills. View spending policy on a Circle agent wallet — per-transaction, daily, weekly, and monthly USDC caps via the circle CLI. Use when the user wants to inspect current limits. Setting or resetting limits requires OTP confirmation in an interactive terminal session — the agent hands the user a verbatim command to run themselves; the OTP must never pass through agent storage. Mainnet-only — testnet chains are rejected. Triggers on: spending limit, spending policy, per-tx cap, daily cap, weekly cap, monthly cap, wallet…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/commands.md`).
It sits in Backend & APIs. It works with Circle USDC. The repository describes itself as: Circle's open source skills for AI-assisted development. The licence is Apache-2.0.
When your agent uses it
The user wants to inspect current limits
: spending limit
Spending policy
OTP confirmation
Example prompts
“/agent-wallet-policy”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 58ab864. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
agents.circle.com
developers.circle.com
console.circle.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agent Wallet Policy loads about 1.7k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 141 tokens; SKILL.md has 877 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~141
When it runs· the whole SKILL.md, loaded when a task matches
~1.7k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~2k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/agent-wallet-policy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
agent-wallet-policy
description
View spending policy on a Circle agent wallet — per-transaction, daily, weekly, and monthly USDC caps via the `circle` CLI. Use when the user wants to inspect current limits. Setting or resetting limits requires OTP confirmation in an interactive terminal session — the agent hands the user a verbatim command to run themselves; the OTP must never pass through agent storage. Mainnet-only — testnet chains are rejected. Triggers on: spending limit, spending policy, per-tx cap, daily cap, weekly cap, monthly cap, wallet rules, OTP confirmation.
Overview
For an overview of the Circle CLI's full capability set, see the use-circle-cli master skill. This skill is the narrower spending-policy flow.
Circle agent wallets support spending policies — per-wallet caps that the CLI enforces on every payment and transfer. There are three operations:
Operation
Command
OTP required?
View current limits
circle wallet limit --address <addr> --chain ARC --output json
No
Set custom limits
circle wallet limit set ...
Yes — human OTP, run in user's own terminal
Reset to defaults
circle wallet limit reset ...
Yes — human OTP, run in user's own terminal
Spending policies are mainnet-only (testnet chains are rejected; see Troubleshooting / Rules).
Prerequisites
Two supporting commands set up the flow: a session check (circle wallet status) and a wallet-address lookup (circle wallet list ... --output json). READ references/commands.md for the exact commands.
If circle wallet status errors with "Not logged in" or "Terms acceptance is required", hand off to the use-agent-wallet skill — it covers install, terms, login, and wallet creation.
Viewing current limits (in-agent, no OTP)
bash
circle wallet limit --address <addr> --chain ARC --output json
Shows the current per-tx, daily, weekly, and monthly USDC caps (null for any unset tier). Safe to call freely — read-only, no money moves, no OTP.
Setting or resetting limits (interactive terminal — handoff to user)
circle wallet limit set and circle wallet limit reset are interactive. They send a 6-digit OTP to the user's email mid-execution and wait for the code at the CLI's stdin prompt.
OTPs are password-equivalent. The agent must NOT receive, store, or relay the OTP. The agent's job here is to hand the user a verbatim command to run in their own terminal, then wait for them to report back.
1. Confirm values with the user
Limits must be monotonic: per-tx ≤ daily ≤ weekly ≤ monthly.
A typical conservative configuration:
Tier
Suggested USDC value
--per-tx
1
--daily
5
--weekly
20
--monthly
50
Adjust based on the user's stated tolerance. Get explicit yes before generating the command.
2. Hand the user the command
Tell the user:
Setting spending limits requires an OTP I shouldn't see. Please run this command in your own terminal — the CLI will email you a 6-digit code; enter it at the prompt. Let me know once it completes.
circle wallet limit reset --address <addr> --chain ARC --yes
Omit --yes if you want the user to see a confirmation prompt before the OTP is sent.
3. Verify after the user reports done
Run the read-only limit command to confirm the new caps, then surface them to the user. READ references/commands.md for the exact command.
Troubleshooting
Symptom
Cause
Fix
User received multiple OTP emails
Command was re-run while a previous invocation was still waiting
Tell the user to use the most recent OTP only. Earlier ones are invalidated.
OTP rejected with "prefix mismatch"
User entered an OTP from a previous request
Restart — each set / reset invocation has a fresh prefix.
Spending policies are mainnet-only
Tried to set a policy on a testnet chain
Re-run with a mainnet --chain value (BASE, MATIC, etc.).
Limits must be monotonic
per-tx > daily, daily > weekly, etc.
Re-check the values. per-tx ≤ daily ≤ weekly ≤ monthly.
Only agent wallets support spending policies
Tried on a local (non-agent) wallet
Spending policies apply only to agent wallets created via circle wallet create.
Show full SKILL.md (332 more words)Show less
Rules
NEVER ask the user to share the OTP with you. The OTP must go directly from the user's email to the CLI prompt in their own terminal — it should never touch the agent's context, tool calls, or any local file.
If email- or messaging-integration tools are connected (e.g., Gmail or Slack via MCP), the OTP can also be fetched through them — note the option to the user; how to handle it is their call.
ALWAYS hand the user a verbatim circle wallet limit set / reset command for them to run in their own terminal. Do NOT try to orchestrate the OTP from chat.
ALWAYS confirm proposed limit values with the user before generating the command. Show the per-tx / daily / weekly / monthly numbers explicitly and wait for explicit yes.
Spending policies are mainnet-only — testnet chains are rejected. Don't quote testnet examples.
Only agent wallets support spending policies, not local wallets.
After the user reports the change is done, run circle wallet limit --address <addr> --chain ARC --output json so the user sees the new caps.
The user has not yet logged in to the CLI or accepted Terms.
circle wallet status errors with "Not logged in" or "Terms acceptance is required".
The user is asking about wallet setup, login, or session state — not policy.
Trigger the pay-via-agent-wallet skill instead when:
The user wants to call, pay for, or use a paid x402 service.
Limits are already set and the user is ready to spend.
Trigger the fund-agent-wallet skill instead when:
The user wants to add USDC before setting limits.
The user mentions deposit, fiat on-ramp, fiat purchase, QR-code transfer, or Gateway deposit.
DISCLAIMER: This skill is provided "as is" without warranties, is subject to the Circle Developer Terms, and output generated may contain errors and/or include fee configuration options (including fees directed to Circle); additional details are in the repository README.
Agent Wallet Policy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Crypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API…
A skill your agent uses when a user needs a QR code or wallet payment URI to fund a Superior-managed EVM wallet on a specific chain before using Lighter, Polymarket, Hyperliquid, or other Superior…
A skill your agent uses when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features.
A skill your agent uses when a developer wants to monetize an API, endpoint, service, model, dataset, tool, or agent-facing resource with Circle USDC pay-per-call payments, Gateway Nanopayments…
A skill your agent uses when the user wants to call a paid API, look something up online, search for data, get prices, odds, or stats, or use any paid service with automatic USDC payment.
View spending policy on a Circle agent wallet — per-transaction, daily, weekly, and monthly USDC caps via the circle CLI. Agent Wallet Policy is an agent skill from circlefin/skills. View spending policy on a Circle agent wallet — per-transaction, daily, weekly, and monthly USDC caps via the circle CLI.
When should I use Agent Wallet Policy?
Agent Wallet Policy fits situations like: the user wants to inspect current limits; : spending limit; spending policy; OTP confirmation.
How do I install Agent Wallet Policy in Claude Code?
Run `npx skills add circlefin/skills --skill agent-wallet-policy -a claude-code`. Or copy the skill folder (plugins/circle/skills/agent-wallet-policy in circlefin/skills) into .claude/skills/agent-wallet-policy in your project. Claude Code loads it when a task matches its description.
How do I install Agent Wallet Policy in Codex?
Run `npx skills add circlefin/skills --skill agent-wallet-policy -a codex`. Or copy the skill folder (plugins/circle/skills/agent-wallet-policy in circlefin/skills) into .agents/skills/agent-wallet-policy in your project. Codex loads it when a task matches its description.
Can I use Agent Wallet Policy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add circlefin/skills --skill agent-wallet-policy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-wallet-policy, .gemini/skills/agent-wallet-policy, .github/skills/agent-wallet-policy and .opencode/skills/agent-wallet-policy in your project.
What does Agent Wallet Policy need to run?
SKILL.md names no scripts, command-line tools or credentials: Agent Wallet Policy is instructions for the agent only.
Does Agent Wallet Policy access the network?
SKILL.md names 3 domains. As links in the text: agents.circle.com, developers.circle.com and console.circle.com. This is read from the text; nothing was executed.
Is Agent Wallet Policy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Agent Wallet Policy use?
Agent Wallet Policy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agent Wallet Policy use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 251 tokens, read only when the agent opens those files.
What are the alternatives to Agent Wallet Policy?
Skills that share tags, products or a category with Agent Wallet Policy: Agentic Wallet (coinbase/agentic-wallet-skills, 127 stars), Deposit Qr (Superior-Trade/superior-skills, 214 stars), Alchemy Agentic Gateway (moonpay/skills, 113 stars) and Mppx (internet-court/internet-court-skill, 6.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agent Wallet Policy?
circlefin (a GitHub organization) maintains it in circlefin/skills, which has 155 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on September 16, 2026.
Source: circlefin/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.