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 picks-trackergit 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/picks-tracker)<a href="https://agentmods.dev/skills/aeonfun/aeon/picks-tracker"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/picks-tracker/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/picks-tracker"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/picks-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 54 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 60 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.00027 | $0.01700 |
| Opus 5.5 | $0.00011 | $0.00680 |
| Sonnet 5.5 | $0.00005 | $0.00340 |
| Haiku 4.5 | $0.00003 | $0.00170 |
Grade A, and why
picks-tracker 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 24d 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` works — there is no network sandbox. For every curl call, if it fails or returns empty/error, use **WebFetch** for the same URL as a fallback for a flaky public GET. Copies of this mod
1 near-identical copy found in the catalogue:
- picks-tracker — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Today is ${today}. Your task is to audit the last 30 days of token picks and score them against current prices.
Read memory/MEMORY.md for context.
Network note
curl works — there is no network sandbox. For every curl call, if it fails or returns empty/error, use WebFetch for the same URL as a fallback for a flaky public GET.
Steps
1. Extract token picks from logs
Scan the last 30 days of memory/logs/ for token picks. For each log file, grep for lines matching **Token:**. Extract:
- Symbol (e.g., XMR, HYPE, TAO)
- Date (from the filename, e.g., 2026-04-19)
- Pick price (the number after
$on the same line, ignoring~approximations)
Also extract prediction market picks from lines matching **Market:**:
- The question text (in quotes)
- The position taken (YES or NO)
- The price/odds at pick time
Expected log format (written by token-pick and monitor-polymarket):
- **Token:** XMR — $350.52 (+1.17% 24h, +2.55% 7d)
- **Market:** "US x Iran permanent peace deal by April 30?" — NO $0.615 (YES 38.5%)
Focus on the last 30 days of logs. If a token was picked multiple times, record each instance separately.
If zero picks are found in the window, log PICKS_TRACKER_SKIP: no picks in last 30 days — enable token-pick / monitor-polymarket and stop (no notification).
2. Fetch current token prices
For each unique token symbol, fetch the current price from CoinGecko.
First, try the search endpoint to get the coin ID. The optional demo key rides ./secretcurl's {COINGECKO_API_KEY} placeholder (never a bare $SECRET on the line); the header is only sent when a key is set:
CG_HDR=(); [ -n "${COINGECKO_API_KEY:+x}" ] && CG_HDR=(-H "x-cg-demo-api-key: {COINGECKO_API_KEY}")
./secretcurl -s "${CG_HDR[@]}" "https://api.coingecko.com/api/v3/search?query=SYMBOL"
Then fetch the price:
./secretcurl -s "${CG_HDR[@]}" "https://api.coingecko.com/api/v3/simple/price?ids=COIN_ID&vs_currencies=usd&include_24hr_change=true"
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.
- 24d ago Changed · -1 lines fdbdb95af9aa
- 25d ago Changed · -1 lines 7c4cee80e604
- 1mo ago First seen · 194 lines · 27 tokens per session scan A 3a7e1f9abef3
picks-tracker is a skill published in the GitHub repository aeonfun/aeon (783 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,700 once invoked, about $0.0001 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
risk-scoring
Score how concentrated and risky a portfolio is on a 0-100 scale from its position weights. Use when the user asks how risky their portfolio is, whether it is too concentrated, or for a diversification check.
valuation
Estimate whether a stock looks cheap or expensive using a price-to-earnings (P/E) based fair-value method. Use when the user asks if a stock is over- or under-valued, or for a fair-value / target price.
comparable-company-analysis
A workflow for comparing a publicly listed company with similar listed companies. It examines their businesses, financial results, competitors, and recent developments.
财经分析工具包
A set of finance analysis tools for stocks, markets, portfolios, and financial news. It includes data retrieval, technical indicators such as moving averages and RSI, trend analysis, risk assessment, and allocation suggestions.
flowcraft-config
Author, validate, and troubleshoot complete FlowCraft configuration: deployment documents (deploy.yaml with the runtime section, inference/workspace/sandbox/tool sub-documents, core/memory contracts, and graph JSON node wiring), craft.yaml application definitions, and plugin.json manifests. Use when writing or…
monetization-strategy
Revenue models, pricing strategies, and business monetization. Use when designing pricing, choosing business models, or optimizing revenue for products and services.