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 aaronjmars/aeon-agent --skill onchain-monitorgit clone --depth 1 https://github.com/aaronjmars/aeon-agentWrote 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/aaronjmars/aeon-agent/onchain-monitor)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/onchain-monitor"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/onchain-monitor/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/aaronjmars/aeon-agent/onchain-monitor"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/onchain-monitor.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.00012 | $0.04124 |
| Opus 5.5 | $0.00005 | $0.01650 |
| Sonnet 5.5 | $0.00002 | $0.00825 |
| Haiku 4.5 | $0.00001 | $0.00412 |
Grade A, and why
onchain-monitor 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 1mo 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.
This is a copy
100% identical to onchain-monitor — 159 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Watch label or chain to check. Empty = all watches.
add-address:<0x… [chain]>is the shape the Telegram force-reply sends — it appends a new watch and exits (see step 0).
If ${var} is set, only monitor the watch with that label or watches on that chain.
Config
Reads memory/on-chain-watches.yml. If the file is missing or watches: [], offer to add the first watch via a Telegram force-reply (only if no add-address prompt was offered in the last 2 days of memory/logs/ — dedup so an unconfigured fork isn't nagged every run), then log ON_CHAIN_NO_CONFIG and exit cleanly (do not send an alert — empty config is not an error):
./notify "No addresses on watch yet. Paste one to monitor — a 0x… wallet, optionally its chain." \
--force-reply --placeholder "0x… base" \
--context "onchain-monitor::add-address"
The reply routes back as var=add-address:<0x… [chain]>, handled by the config-capture branch in step 0. Record FORCE_REPLY_OFFERED: add-address in the log when you send it.
# memory/on-chain-watches.yml
watches:
- label: My Wallet
address: "0x1234...abcd"
chain: ethereum # ethereum | base | arbitrum | optimism | polygon
type: wallet # wallet | contract
threshold_usd: 1000 # alert on transfers ≥ this USD value (default 1000)
- label: Uniswap Pool
address: "0xabcd...5678"
chain: ethereum
type: contract
event_topics: # optional — only alert on these topic0 hashes
- "0xddf252ad..." # ERC20 Transfer
Optional memory/known-addresses.yml — counterparty label dictionary used to humanize alerts. Lowercase keys, free-text values:
labels:
"0x28c6c06298d514db089934071355e5743bf21d60": "Binance 14"
"0xa9d1e08c7793af67e9d92fe308d5697fb81d3e43": "Coinbase 10"
"0xe592427a0aece92de3edee1f18e0157c05861564": "Uniswap V3 Router"
"0x0000000000000000000000000000000000000000": "Zero (mint/burn)"
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.
- 1mo ago First seen · 272 lines · 12 tokens per session scan A 747f0bbb3eca
onchain-monitor is a skill published in the GitHub repository aaronjmars/aeon-agent (12 stars, last pushed 12d ago), licensed MIT. It adds 12 tokens to every session and 4,124 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to onchain-monitor, differing in 159 lines, and is treated as a copy.
Other skills, from other repositories
strategy-spec
Generates a backtestable, regime-gated mean-reversion TRADING STRATEGY SPEC for a BSC / PancakeSwap token using CoinMarketCap x402 DEX data — and decides what data is even worth paying for first (honest free-vs-paid routing). Produces rules + parameters + a 180-day backtest with a buy-and-hold benchmark. A strategy…
aawp
AAWP (AI Agent Wallet Protocol) — the only crypto wallet protocol built exclusively for AI Agents on EVM-compatible blockchains and Solana. Not for humans. The signer is the AI Agent itself, cryptographically bound at wallet creation. Supports wallet lifecycle management, token transfers, DEX swaps, cross-chain…
clicks-protocol
Integrate Clicks Protocol settlement routing into AI agent projects on Base. Use when building agents that hold, earn, receive, or transfer USDC, when asked about agent treasury management, x402 payment settlement, idle USDC routing, or agent referral attribution.
clicks
Write and read on-chain agent reputation on Base via ERC-8004. Use when an AI agent finishes a task and needs to attest the outcome, or before delegating to another agent when trust matters. Backed by the Clicks Protocol Attestor Schema V1 on Base mainnet.
alien-plugg-x402
38 paid x402 API endpoints for AI agents — Zora crypto analysis, Robinhood Chain tokenized stocks, on-chain intelligence, whale tracking, and utilities. MCP-compatible. Flat $0.003/call via USDC micropayments on Base.
agentpay-route
Find, judge, and pay for the best paid x402 tool/API for a need, within a budget. Use when the agent needs a capability behind a paid API and must choose a provider: "which x402 service / paid API for X", "find a tool for X under $Y", comparing providers, avoiding overpriced or fake/stub endpoints, or routing agent…