Borrowing it
Nothing to install: this file belongs to rickycambrian/geo_mcp_server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rickycambrian/geo_mcp_server/main/.claude/skills/wallet-approval-mode/SKILL.mdgit clone --depth 1 https://github.com/rickycambrian/geo_mcp_serverWrote 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/rickycambrian/geo_mcp_server/wallet-approval-mode)<a href="https://agentmods.dev/skills/rickycambrian/geo_mcp_server/wallet-approval-mode"><img src="https://agentmods.dev/badge/skills/rickycambrian/geo_mcp_server/wallet-approval-mode/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rickycambrian/geo_mcp_server/wallet-approval-mode"><img src="https://agentmods.dev/badge/skills/rickycambrian/geo_mcp_server/wallet-approval-mode.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01451 |
| Opus 5 | $0.00020 | $0.00726 |
| Sonnet 5 | $0.00008 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
wallet-approval-mode 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 10d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wallet Approval Mode
The Geo MCP server supports two wallet modes that determine how write operations handle blockchain transactions:
- PRIVATE_KEY (default): Server holds the private key, signs and sends transactions immediately.
- APPROVAL: Server returns unsigned transaction data as
{ status: 'pending_signature', ... }for external wallet signing.
Core Architecture
executeTransaction() — the dual-mode abstraction
All write operations use executeTransaction(session, request) instead of calling smartAccountClient.sendTransaction() directly.
File: src/utils/tx-executor.ts
const txResult = await executeTransaction(session, {
to: contractAddress,
data: calldata,
description: 'Human-readable action description',
toolName: 'publish_edit',
metadata: { editId, cid },
});
if (txResult.mode === 'pending_approval') {
return ok({ status: 'pending_signature', ...txResult.pendingTx });
}
// mode === 'executed' — continue with existing flow using txResult.txHash
Session state for APPROVAL mode
File: src/state/session.ts
The EditSession class tracks:
walletMode: 'PRIVATE_KEY' | 'APPROVAL'pendingTransactions: PendingTransaction[]— unsigned txs waiting for external signingcontinuations: Map<string, TransactionContinuation>— maps pendingTxId to next step
clear() resets pendingTransactions and continuations along with ops/artifacts.
getStatus() returns mode: 'approval' when walletMode === 'APPROVAL' && walletAddress !== null.
configure_wallet extension
File: src/tools/spaces.ts
The tool accepts optional walletAddress and walletMode params:
walletMode='APPROVAL'+walletAddressconfigures without private key- Does NOT call
getSmartAccountWalletClient - Sets
session.walletModeandsession.walletAddress
ensureWalletConfigured() early return
File: src/utils/wallet.ts
APPROVAL mode check goes BEFORE the private key cascade:
if (session.walletMode === 'APPROVAL' && session.walletAddress) {
return { ok: true, address: session.walletAddress as Hex };
}
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.
- 10d ago First seen · 144 lines · 41 tokens per session scan A a45547a57858
wallet-approval-mode is a skill published in the GitHub repository rickycambrian/geo_mcp_server (0 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,451 once invoked, about $0.0002 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 skills, from other repositories
web3-fullstack-packaged-build
Systematic full-stack Web3 build with mandatory packaging and delivery phase.
web3-fullstack-systematic-build
Systematic approach to building full-stack Web3 applications layer by layer.
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
walkeros-create-destination
Use when creating a new walkerOS destination to send events to a vendor or API (GA4/gtag, Meta/Facebook Pixel, Mixpanel, Amplitude, a custom HTTP API, Measurement Protocol), web or server-side. Example-driven workflow: research the vendor SDK and define step examples before implementing the destination interface, env…
walkeros-create-source
Use when creating a new walkerOS source to capture events (browser source, dataLayer interception, server/HTTP source, webhook receiver, event capture), web or server-side. Example-driven workflow: research the input format and define step examples before implementing the push interface, createTrigger, and env pattern.