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 sc-auditgit 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/sc-audit)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/sc-audit"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/sc-audit/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/sc-audit"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/sc-audit.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.00094 | $0.18667 |
| Opus 5.5 | $0.00038 | $0.07467 |
| Sonnet 5.5 | $0.00019 | $0.03733 |
| Haiku 4.5 | $0.00009 | $0.01867 |
Grade B, and why
sc-audit scanned grade B with 2 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$WORKDIR/.scan/$FIXTURE"; cp -r "$SRC" "$WORKDIR/.scan/$FIXTURE" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o "$SCRATCH/sourcify.json" \ This is a copy
100% identical to sc-audit — 0 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 — 713 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} - Target selector. Four forms:
- `` (empty) -> auto-select the day's fresh feed target, audit only if it contains Solidity, else exit clean. See §S1 for the selection order (an optional
sc-targets.jsonledger, else thegithub-trendingfeed).owner/repo-> audit that GitHub repo (e.g.Uniswap/v4-core,aave/aave-v3-origin).<chain>:0x<address>-> on-chain mode: audit a live deployed contract by address. It fetches the verified source from the block explorer (Etherscan V2) or Sourcify, materializes it as a Foundry project, and runs the same pipeline - plus on-chain context (proxy/implementation, owner/admin, funds at risk).chainineth/base/arbitrum/optimism/polygon/bsc/... (bare0x<address>defaults toeth). Examples:base:0x4200000000000000000000000000000000000006,eth:0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2. On-chain findings are operator-gated - never auto-filed/auto-emailed (see §S7). See §S1/§S2.fixture:<name>-> local regression mode: audit the bundled fixture atskills/sc-audit/fixtures/<name>/(e.g.fixture:vault). No fork, no dedup, no disclosure - a self-contained way to exercise the whole pipeline including the fuzz arm, with no external repo. See §S1/§S2.
Today is ${today}. Read memory/MEMORY.md and the last 30 days of memory/logs/ before starting.
Why this skill exists
Smart-contract bugs are logic and economics, not syntax. Slither matches known static patterns; it is weak on access control, protocol invariants, oracle/price manipulation, rounding/precision, upgradeability storage collisions, and cross-contract reentrancy - the classes that actually drain funds, and where exploitation on-chain is immediate and irreversible. That whole class is what an agentic reviewer catches by reading the source and reasoning about who can call what and which invariant breaks.
This skill is the contract arm split out of vuln-scanner. vuln-scanner detects Solidity and hands the repo here rather than running Slither inline; this skill owns the deep audit and then routes findings through vuln-scanner's shared disclosure machinery. It does not duplicate the disclosure/PVR/email logic - see §S7.
It audits two kinds of target: a GitHub repo (source in a repo you fork), and a live contract deployed on-chain by address (<chain>:0x<addr>) - the latter fetches the verified source from the block explorer/Sourcify and adds on-chain context (proxy/implementation, owner, funds at risk). A live deployed contract is where a bug is already exploitable with real money at stake, so on-chain findings are treated as the highest-stakes disclosure and are operator-gated - staged for a human, never auto-filed (§S7).
The agentic source pass is the reliable core. Slither is best-effort: a headless run has slither allow-listed but not solc / forge / solc-select, so contracts that need a compiler to build may not compile in-run. The source pass needs no compiler, so a clean audit never depends on Slither succeeding.
What ships with it
4 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 · 713 lines · 94 tokens per session scan B 7bd9c496734e
sc-audit is a skill published in the GitHub repository aaronjmars/aeon-agent (12 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 18,667 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). It is 100% identical to sc-audit, differing in 0 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…