arbitrage-scanner

arbitrage-scanner is a skill for Claude Code, Codex from Virtual-Protocol/acp-cli-demos. It costs 0 tokens per session (640 once invoked), scanned A, original, no licence file.

A scanner for finding price differences between Uniswap v3 and Aerodrome, two crypto exchanges on the Base network. It estimates the possible profit after network fees and flash-loan fees, then assesses the opportunity.

In plain words
What is it for?
Use it to review cross-exchange arbitrage opportunities on Base, including the price difference, estimated net profit, and overall assessment.
Why use it?
It helps you judge whether a price gap may still be worthwhile after transaction costs. It removes the need to compare both exchanges and calculate those costs manually.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/virtual-protocol/acp-cli-demos/arbitrage-scanner
Any agent
npx skills add Virtual-Protocol/acp-cli-demos --skill arbitrage-scanner
Clone the repo
git clone --depth 1 https://github.com/Virtual-Protocol/acp-cli-demos

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for arbitrage-scanner

README.md
[![agentmods](https://agentmods.dev/badge/skills/virtual-protocol/acp-cli-demos/arbitrage-scanner.svg)](https://agentmods.dev/skills/virtual-protocol/acp-cli-demos/arbitrage-scanner)
Your own site
<a href="https://agentmods.dev/skills/virtual-protocol/acp-cli-demos/arbitrage-scanner"><img src="https://agentmods.dev/badge/skills/virtual-protocol/acp-cli-demos/arbitrage-scanner.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 640 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00640
Opus 5 $0.00000 $0.00320
Sonnet 5 $0.00000 $0.00128
Haiku 4.5 $0.00000 $0.00064

Measured 3d ago against content hash 5c582151c2d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

arbitrage-scanner 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 3d 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.

showcase/kernal/skills/arbitrage-scanner/SKILL.md · 76 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 76 lines · 0 tokens per session scan A 5c582151c2d1

Subscribe to this mod's changes

arbitrage-scanner is a skill published in the GitHub repository Virtual-Protocol/acp-cli-demos (22 stars, last pushed 17d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 640 tokens. 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens