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 skills/orbs-network/spot/skillnpx skills add orbs-network/spot --skill skillgit clone --depth 1 https://github.com/orbs-network/spotWhat 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.00035 | $0.01004 |
| Opus 5 | $0.00017 | $0.00502 |
| Sonnet 5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
spot-advanced-swap-orders 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 yesterday.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spot Advanced Swap Orders
Use this skill when the agent needs to turn user intent into a final Spot order payload on a supported EVM chain. It covers order-shape selection, param normalization, typed-data population, approval guidance, signing, submission, query, and cancellation. This bundle is instruction-only: build everything locally from the bundled markdown and JSON assets, then submit only the final signed payload. Execution remains decentralized, non-custodial, oracle-protected, immutable, audited, and battle-tested onchain.
Supported Chains
- Ethereum -
1 - Optimism -
10 - Flare -
14 - BNB Chain -
56 - Unichain -
130 - Polygon -
137 - Monad -
143 - Sonic -
146 - X Layer -
196 - HyperEVM -
999 - Sei -
1329 - MegaETH -
4326 - Base -
8453 - Arbitrum One -
42161 - Avalanche -
43114 - Linea -
59144 - Berachain -
80094 - Katana -
747474
The bundled JSON template hardcodes the shared agent adapter. Do not derive or replace the adapter per chain.
Relay
- Submit signed orders with
POST https://agents-sink.orbs.network/orders/new. - Query orders with
GET https://agents-sink.orbs.network/orders; see references/lifecycle.md for filters, polling, and cancellation follow-up.
Workflow
- Read references/quickstart.md for the minimum end-to-end flow.
- Use references/params.md to map user intent into params, defaults, validation, and order-shape fields.
- Use references/sign.md to fill the template, handle approval, sign, and submit.
- Use references/lifecycle.md for relay query semantics, status polling, and cancellation.
- Use references/examples.md only when the final relay payload shape is still unclear.
- Use assets/token-addressbook.md only for optional token alias lookup on supported chains.
- Use assets/repermit.template.json as the canonical typed-data shape.
- Treat
## Supported Chainsas the authoritative source for chain support. - Treat
## Relayas the authoritative relay endpoint list.
What ships with it
9 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.
- yesterday First seen · 79 lines · 35 tokens per session scan A ace3e9153644
spot-advanced-swap-orders is a skill published in the GitHub repository orbs-network/spot (2 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 1,004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…