Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GeckoVision/gecko-surfnpx agentmods add skills/geckovision/gecko-surf/x402-payai-setupWrote 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/geckovision/gecko-surf/x402-payai-setup)<a href="https://agentmods.dev/skills/geckovision/gecko-surf/x402-payai-setup"><img src="https://agentmods.dev/badge/skills/geckovision/gecko-surf/x402-payai-setup/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/geckovision/gecko-surf/x402-payai-setup"><img src="https://agentmods.dev/badge/skills/geckovision/gecko-surf/x402-payai-setup.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.00122 | $0.01186 |
| Opus 5 | $0.00061 | $0.00593 |
| Sonnet 5 | $0.00024 | $0.00237 |
| Haiku 4.5 | $0.00012 | $0.00119 |
Grade A, and why
x402-payai-setup 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
x402 + PayAI Setup Skill
Do
api-agent-readyfirst. This skill assumes the API is already comprehended and served over MCP. It adds pay-per-call on top — the provider charging agents for priced operations, settled over the x402 rail via PayAI.
What this skill is for
Some operations are worth money. A provider who wants agents to pay for calls needs the payment handshake wired into the tools the agent already uses — without Gecko ever holding funds or taking a cut.
The mechanism is x402: an HTTP-native micropayment flow. A priced endpoint
answers an unpaid request with 402 Payment Required and a challenge; the agent
attaches a payment and retries; a facilitator (PayAI, on Solana) verifies and
settles; the endpoint returns 200 + the data. Gecko's only job is
comprehension: point the agent-facing tool at the provider's own x402 endpoint
and surface the handshake so the agent knows to pay.
The line we never cross
Provider-pays for comprehension; provider keeps 100% of call revenue; Gecko is never the rail.
- The money flows agent → provider, settled by PayAI. Gecko is not in the money path and takes no take-rate.
- We compose the rail (PayAI / Metera / pay.sh) — we do not build one and do not become a marketplace.
- We never custody, never sign, never broadcast. Live settlement is founder-gated
and defaults to
X402_MODE=stub.
If any step routes money through Gecko or adds a cut, stop — re-read
rules/aggregate-not-rail.md.
The three-step spine
| # | Step | Read | Status |
|---|---|---|---|
| 1 | Map priced ops — which operations sit behind x402 vs stay free | this file, below | provider's toggle |
| 2 | Wire x402 via PayAI — point tools at the provider's x402 endpoint | wire-x402-payai.md | Building / founder-gated |
| 3 | Verify offline first — prove the paid-call shape before live settlement | verify-paid-call.md | Building — offline stub (X402_MODE=stub) |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 87 lines · 122 tokens per session scan A facef9460502
x402-payai-setup is a skill published in the GitHub repository GeckoVision/gecko-surf (6 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 1,186 once invoked, about $0.0006 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
aomi-build
Scaffold new Aomi apps and plugins from API docs, OpenAPI/Swagger specs, or SDK references. aomi-build generates production-ready Rust SDK crates (lib.rs, client.rs, tool.rs) with tool schemas, preambles, host-interop flows, and validation — turning a vendor's API surface into AI-agent-callable tools. It covers the…
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
web3-fullstack-packaged-build
Systematic full-stack Web3 build with mandatory packaging and delivery phase.
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.