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 token-moversgit 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/token-movers)<a href="https://agentmods.dev/skills/aeonfun/aeon/token-movers"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/token-movers/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/token-movers"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/token-movers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 18 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 analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- medium Excessive Agency · line 41 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Data Exfiltration · line 78 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 81 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 232 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 238 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 241 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 247 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 439 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 440 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 442 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 443 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 444 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 439 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 452 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 484 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 592 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 592 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.00042 | $0.11571 |
| Opus 5.5 | $0.00017 | $0.04628 |
| Sonnet 5.5 | $0.00008 | $0.02314 |
| Haiku 4.5 | $0.00004 | $0.01157 |
Grade A, and why
token-movers 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 19d 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.
If curl fails or returns empty JSON, retry once with **WebFetch** against the same URL. Copies of this mod
1 near-identical copy found in the catalogue:
- token-movers — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 693 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — selects the scan. Two behavioral modes (
movers,single-token) over two sources (coingecko,geckoterminal):
- empty → movers scan on the default source (CoinGecko): top winners, losers, trending.
coingecko→ same movers scan, CoinGecko source (explicit).geckoterminal→ movers scan on GeckoTerminal: on-chain "runners" across major chains.geckoterminal:<chain>or a bare chain slug (solana,eth,ethereum,base,bsc,arbitrum,polygon,optimism,avalanche,avax) → GeckoTerminal runners scoped to that one chain.category:<name>(e.g.category:layer-2,category:meme) — or a bare hyphen/space value likelayer-2/meme coins→ CoinGecko movers scoped to that category.<contract>or<contract>:<chain>(e.g.0xabc…,0xabc…:base) → single-token deep report on that contract.<SYMBOL>(e.g.SOL,WIF) → single-token deep report; resolve the symbol to its top contract first.token/single-token→ single-token deep report on the token configured inmemory/token-report.md.deep-dive:<symbol|contract>(e.g.deep-dive:WIF,deep-dive:0xabc…:base) → single-token deep report — the shape the Telegram force-reply sends. Strips thedeep-dive:prefix and resolves the remainder exactly like a bare symbol/contract.Examples:
""(global movers),geckoterminal:base(Base runners),category:layer-2(L2 movers),0x4ed…:baseorWIF(single-token report).
Preamble (every run)
-
Read
memory/MEMORY.mdfor context. -
Read the last 2 days of
memory/logs/to avoid repeating the same movers/trending/runner names unless the move is materially different — repeat runners across days are the real signal. (The single-token branch reads the last 30 days for itsTOKEN_REPORT_STATE:delta lines — see that branch.) -
Parse
${var}→source+mode(+ optionaltoken/chain/category). Trim whitespace; evaluate the rules top-to-bottom, first match wins (fully deterministic):- Force-reply intercept (Telegram deep-dive). starts with
deep-dive:→ strip the prefix (${var#deep-dive:}) and treat the remainder EXACTLY as a single-token target, resolving it contract-or-symbol just like rule 8 (token:) does → single-token. Single-token branch. This is the shape the Telegram force-reply sends; it reuses all existing single-token logic (no separate handler, no confirmation — the single-token report IS the response). - empty → mode=movers, source=coingecko (global). Go to Movers branch.
coingecko(case-insensitive) → movers / coingecko (global). Movers branch.geckoterminal→ movers / geckoterminal (all major networks). Movers branch.- starts with
geckoterminal:orchain:→ movers / geckoterminal,chain= remainder. Movers branch. - a known chain slug (
solana|eth|ethereum|base|bsc|arbitrum|polygon|optimism|avalanche|avax) → movers / geckoterminal,chain= value. Movers branch. (Preserves monitor-runners'var=chain behaviour. To report on a token that shares a chain name, e.g. the ETH token, usetoken:ethor its contract.) - starts with
category:→ movers / coingecko,category= remainder. Movers branch. - equals
tokenorsingle-token→ single-token, token frommemory/token-report.mdconfig. Single-token branch. - starts with
token:→ single-token, resolve remainder as contract-or-symbol. Single-token branch. - matches a contract address — EVM
0x[0-9a-fA-F]{40}or a Solana base58 address — optionally:chain→ single-token, that contract. Single-token branch. - contains a space or a hyphen and is not a contract (e.g.
layer-2,meme coins) → movers / coingecko,category= value. Movers branch. - otherwise (a bare word, a plausible ticker) → single-token / geckoterminal, resolve
symbol= value to its top contract. Single-token branch.
- Force-reply intercept (Telegram deep-dive). starts with
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.
- 19d ago Changed · +1 lines 1df5b692ce40
- 1mo ago First seen · 692 lines · 42 tokens per session scan A 8f0226dbd33b
token-movers is a skill published in the GitHub repository aeonfun/aeon (778 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 11,571 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-09-05.
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.