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.
git clone --depth 1 https://github.com/GeckoVision/gecko-surfWrote 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/commands/geckovision/gecko-surf/setup-x402)<a href="https://agentmods.dev/commands/geckovision/gecko-surf/setup-x402"><img src="https://agentmods.dev/badge/commands/geckovision/gecko-surf/setup-x402.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.00069 | $0.00589 |
| Opus 5 | $0.00034 | $0.00295 |
| Sonnet 5 | $0.00014 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
setup-x402 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.
What it actually says
/setup-x402
Wire x402 micropayments onto a provider's API via PayAI, offline-first. Run
/make-agent-ready first — this assumes the API is already comprehended and served.
Argument: the API (already agent-ready) whose priced operations you're wiring.
Steps
- Map priced ops. With the provider, decide which comprehended operations are
priced vs free. Capture, per priced op, the amount (atomic units), the asset, and
the provider's
payToaddress. These are the provider's values, not Gecko's. - Wire x402 via PayAI. Point the agent-facing tool at the provider's own
x402-priced endpoint and surface the
402challenge so the agent knows to pay. Confirm the PayAI facilitator URL/SDK against live docs; flag anything unverified<!-- VERIFY -->. Gecko hosts no payment endpoint. (Seeskills/x402-payai-setup/wire-x402-payai.md.) - Verify offline. Keep the default
X402_MODE=stub. Run the full 402 → pay → 200 shape with no spend and assert: 402 well-formed,amountin atomic units,payTois the provider's, paid→200, no secret leaks. (Seeskills/x402-payai-setup/verify-paid-call.md.) - Hand off for live (founder-gated). Prepare the go-live command; the founder
sets
X402_MODElive and broadcasts. One live smoke, then stop. Claude never signs or broadcasts.
Notes
- Compose the rail, take no cut. Money flows agent → provider, settled by PayAI. Gecko is never in the money path; the provider keeps 100%.
payTois the provider's, never Gecko's. If it ever isn't, that's a bug.- Default
X402_MODE=stub; never flip to live without founder go-ahead. Never sign or broadcast — founder-run only. - Offline-first (Pattern B). The stub handshake is the deliverable and the debugger; live smoke is the final confirmation.
- Status: the handshake shape + offline verification are buildable today; live PayAI settlement is Building / founder-gated. Don't overclaim.
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 · 42 lines · 69 tokens per session scan A 42ab96db1ea7
setup-x402 is a command published in the GitHub repository GeckoVision/gecko-surf (6 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 589 once invoked, about $0.0003 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.