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 agentmods add commands/techgangboss/agentstore/walletgit clone --depth 1 https://github.com/techgangboss/agentstoreWhat 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 | $0.00009 | $0.00575 |
| Opus 5 | $0.00005 | $0.00287 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
wallet 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 2d 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.
What it actually says
AgentStore Wallet
Manage your local wallet for x402 payments on Base network.
Instructions
Based on the action parameter (default: status):
status
- Check if wallet exists at
~/.agentstore/wallet.json - If exists, display:
## AgentStore Wallet **Address:** 0x... **Network:** Base (Chain ID: 8453) **USDC Balance:** $X.XX **Spend Limits:** - Per transaction: $50.00 - Daily: $100.00 (remaining: $X.XX) - Weekly: $500.00 (remaining: $X.XX) - If no wallet: "No wallet configured. Run
/wallet setupto create one."
setup
- Ask user: "Create a new wallet or import existing?"
- For new wallet:
- Generate new keypair using viem
- Encrypt private key with password
- Save to
~/.agentstore/wallet.json - Display address and backup seed phrase warning
- For import:
- Prompt for private key or seed phrase
- Encrypt and save
- Set default spend limits
fund
- Display wallet address for deposits
- Show QR code if possible
- Provide link to Coinbase for purchasing USDC on Base:
To add funds: 1. Send USDC (Base network) to: 0x... 2. Or use Coinbase: https://www.coinbase.com/ Minimum recommended: $10.00 USDC
history
- Read transaction history from local storage
- Display recent purchases:
## Transaction History | Date | Agent | Amount | Status | |------|-------|--------|--------| | Jan 3 | SQL Expert | $5.00 | Confirmed |
limits
- Display current spend limits
- Ask if user wants to modify:
- Per-transaction limit (default $50)
- Daily limit (default $100)
- Weekly limit (default $500)
- Save updated limits
Files
~/.agentstore/
wallet.json # Encrypted wallet config
history.json # Transaction history
entitlements/ # Stored entitlement tokens
Security Notes
- Private key encrypted with AES-256-GCM
- Never transmitted over network
- Spend limits enforced client-side before signing
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.
- 2d ago First seen · 91 lines · 9 tokens per session scan A 0a57a403f361
wallet is a command published in the GitHub repository techgangboss/agentstore (4 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 575 once invoked, about $0.0000 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.