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 aeonfun/aeon --skill defi-overviewgit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/defi-overview)<a href="https://agentmods.dev/skills/aeonfun/aeon/defi-overview"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/defi-overview/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/aeonfun/aeon/defi-overview"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/defi-overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 10 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 84 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 143 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 144 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 146 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 147 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 159 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 161 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 163 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 165 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 168 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00046 | $0.07529 |
| Opus 5.5 | $0.00018 | $0.03012 |
| Sonnet 5.5 | $0.00009 | $0.01506 |
| Haiku 4.5 | $0.00005 | $0.00753 |
Grade A, and why
defi-overview scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "${rpc_url}" \ Copies of this mod
1 near-identical copy found in the catalogue:
- defi-overview — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Scope selector. Empty → full combined overview (tracked-protocol positions + macro context).
positions→ positions facet only (all watched positions);positions:<label>→ a single tracked position by label.macro→ macro facet only. Any other value → treat as a chain or protocol focus (e.g.solana,aave,arbitrum) applied to the macro read; positions are filtered to that chain when applicable.
Read memory/MEMORY.md for context. Read the last 2 days of memory/logs/ to avoid repeating numbers, to diff position values over time, and to cite yesterday's figure when flagging today's change. Read memory/on-chain-watches.yml (tracked positions) and the existing memory/topics/market-context.md (prior macro snapshot) — both are inputs below.
Thesis
The original produced a table of numbers. This version produces a read of the market: one verdict line at the top, then only items that changed or matter, each with a one-line reason a reader should care. TVL alone is lagging and emission-subsidized — we pair it with fees/revenue (real fundamentals) and split yields into sustainable (apyBase) vs incentive-driven (apyReward) so readers stop chasing scam-tier APYs. On top of the market read this skill also (a) checks the operator's tracked-protocol positions for health/liquidation/yield-drift risk, and (b) refreshes the decision-ready macro context file that downstream skills (token-pick, narrative-tracker) consume — all in one pass.
Facets & var routing
The skill has two facets. ${var} selects which run and how to scope them:
- Empty → run both facets: Positions and Macro. This is the comprehensive default.
positions→ Positions facet only, all watched positions.positions:<label>→ Positions facet only, restricted to the position whoselabelmatches<label>.macro→ Macro facet only (DeFi market read + broad crypto context +market-context.mdrefresh).- Any other value → Macro facet, run in focus mode:
- matches a chain name in
/v2/chains(case-insensitive) → chain focus: scope DEX volume, fees, and yields to that chain; keep a 2-line market header for context; filter positions (if the Positions facet also runs) to that chain. - matches a protocol slug in
/protocols→ protocol focus: pull/protocol/{slug},/summary/fees/{slug},/summary/dexs/{slug}if it is a DEX; compare against its chain and its 30-day self. - matches neither → proceed as a full macro overview and note
var unresolved: ${var}in the footer.
- matches a chain name in
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 · 474 lines · 46 tokens per session scan A 01e96f1e5657
defi-overview is a skill published in the GitHub repository aeonfun/aeon (782 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 7,529 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
crypto-sage
Activates CryptoSage for crypto, DeFi, and Web3 intelligence. Use when you need on-chain analytics (MVRV, SOPR, NVT, exchange flows), DeFi TVL trend analysis, tokenomics review (vesting schedules, inflation rate, unlock impact), narrative momentum tracking, or rug pull / audit risk assessment.
solana
Query Solana blockchain data with USD pricing — wallet balances, token portfolios with values, transaction details, NFTs, whale detection, and live network stats. Uses Solana RPC + CoinGecko. No API key required.
evm
Read-only EVM client: wallets, tokens, gas across 8 chains.
hyperliquid
Hyperliquid market data, account history, trade review.
solana
Query Solana wallets, tokens, txs, and NFTs in USD.
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and flash loans. Use when building decentralized finance applications or smart contract protocols.