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 skills add sepivip/SeekerClaw --skill paysh-cataloggit clone --depth 1 https://github.com/sepivip/SeekerClawWrote 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/sepivip/seekerclaw/paysh-catalog)<a href="https://agentmods.dev/skills/sepivip/seekerclaw/paysh-catalog"><img src="https://agentmods.dev/badge/skills/sepivip/seekerclaw/paysh-catalog/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/sepivip/seekerclaw/paysh-catalog"><img src="https://agentmods.dev/badge/skills/sepivip/seekerclaw/paysh-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.04207 |
| Opus 5 | $0.00045 | $0.02103 |
| Sonnet 5 | $0.00018 | $0.00841 |
| Haiku 4.5 | $0.00009 | $0.00421 |
Grade A, and why
paysh-catalog 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pay.sh Service Catalog
A curated directory of HTTPS endpoints the agent can pay for using agent_pay and the burner wallet, only when the user explicitly opts in via a pay-intent keyword.
Default: this skill is DORMANT
For the vast majority of user messages, this skill should not activate. The agent's default behavior for any question is:
- Try training data (facts, definitions, well-established knowledge)
- Try
web_search/web_fetch(live web data, free) - If neither answers and the user did NOT explicitly invoke pay/x402, give a best-effort honest answer noting the limitation — do NOT autonomously reach for a paid catalog service
This skill activates ONLY when the user's message contains one of the explicit pay-intent keywords listed below. If you're unsure whether a message is opting in, prefer the free path — paid lookups cost USDC and the user did not authorize a charge implicitly.
Opt-in keywords (skill activates)
The authoritative activation contract is the triggers: list in this file's frontmatter (BAT-1035). The skill activates only when the user's message contains one of those exact phrases:
pay.sh/paysh— naming the platformx402— naming the protocolpay with burner— explicit burner-pay intentpay for— explicit paying verbwhat can you pay for/show me pay.sh services/list paid services— capability question
Intentionally NOT triggers: pay to <person> (that is a normal SOL/SPL transfer — use solana_send, not a paid API) and pay with main (agent_pay settles from the burner only, never the main wallet). If a message is ambiguous, prefer the free path — paid lookups cost USDC and the user did not authorize a charge implicitly.
NOT opt-in (skill stays dormant)
- Topical / factual questions: "what's the mass of the sun", "who founded Solana", "what time is it in Tokyo" → training data or
web_search - Live-data questions WITHOUT a paying verb: "find me a hotel in Rome", "current price of SOL", "best deal on a PS5" →
web_search - General Solana / Jupiter operations: "check my balance", "send 0.1 SOL to Alice", "swap SOL for USDC" → use the relevant tool directly (
solana_balance,solana_send,solana_swap); these are NOT x402 and don't involve this skill
What ships with it
14 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.
- catalog.json 52 KB
- SCHEMA.md 21 KB
- services/2captcha.md 2.5 KB
- services/crushrewards.md 4.4 KB
- services/perplexity.md 8.9 KB
- services/purch.md 1.3 KB
- services/reducto.md 2.3 KB
- services/rentcast.md 8.7 KB
- services/stablecrypto-market-data.md 14 KB
- services/stableenrich.md 1.3 KB
- services/textbelt-sms.md 4.8 KB
- services/tripadvisor.md 3.2 KB
- services/wolfram-alpha.md 3.5 KB
- unsupported.json 94 KB
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 · 192 lines · 90 tokens per session scan A 1fd8d6d1a12e
paysh-catalog is a skill published in the GitHub repository sepivip/SeekerClaw (314 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 4,207 once invoked, about $0.0005 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-30.
Other skills, from other repositories
android-expert
Expert in Android development with Jetpack Compose, Material Design, ViewModel, and modern Android architecture. Use when the user mentions mobile, Kotlin, Jetpack Compose, Material Design, or Google, or when the task involves Android Architecture, Android Components, Jetpack Libraries, or Activity/Fragment Lifecycle.
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
sceneview-web
Build 3D and WebXR (AR/VR) experiences in the browser with SceneView for Web — Filament.js (WebGL2/WASM) wrapped in a Kotlin/JS DSL and a plain-JavaScript API on window.sceneview. Use whenever the user asks for "3D in the browser", "a web model viewer", "WebXR AR/VR", or any browser 3D/AR app where the dependency is…
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
to-plan
Use when one ready GitHub issue or an in-chat task needs a repository-aware implementation plan for a later implementation workflow.
compose-ui-testing-patterns
Use when writing or reviewing Jetpack Compose UI tests, screenshot tests, previews, semantics assertions, fake image loading, keyboard input, focus assertions, interaction state (hover/pressed/focused), or tests for plain state-driven UI composables.