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 github-trendinggit 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/github-trending)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/github-trending"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/github-trending/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/github-trending"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/github-trending.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.00043 | $0.05539 |
| Opus 5.5 | $0.00017 | $0.02216 |
| Sonnet 5.5 | $0.00009 | $0.01108 |
| Haiku 4.5 | $0.00004 | $0.00554 |
Grade A, and why
github-trending 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 23d 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.
Fetch the daily trending page via **WebFetch** (it renders the HTML for you; `curl` works too — there is no network sandbox): This is a copy
100% identical to github-trending — 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Source selector plus optional sub-scope:
- empty or
github→ GitHub trending, all languages (default)github:<lang>— or a bare language token likepython,typescript,rust(backward-compatible with the old GitHub var) → GitHub trending filtered to that languagehforhuggingface→ Hugging Face trending across models + datasets + spaceshf:models/hf:datasets/hf:spaces(alsohuggingface:models, etc.) → Hugging Face trending scoped to a single resource type
This skill covers two neighbouring layers of where developer/AI attention is moving today: the repo layer (GitHub trending) and the artifact layer (Hugging Face Hub — the models, datasets, and spaces that ship alongside, and frequently before, the paper). Both branches share the same contract: don't dump the top 10 (the source's own front page already does that) — deliver a curated slate of 5–8 picks a busy reader would actually want to click, grouped by category, with a one-line "why notable" and a momentum tag per pick.
Shared preamble (run for every invocation)
Read memory/MEMORY.md for context.
Read the last 3 days of memory/logs/ to dedupe items you've already featured (the GitHub branch dedupes against the last 2 days, the Hugging Face branch against the last 3 — see each branch's filter step).
Read soul/SOUL.md + soul/STYLE.md if populated to match voice.
Parse ${var} into a source + optional sub-scope (deterministic):
- If
${var}is empty → GitHub branch, no language filter. - Otherwise trim + lowercase and split on the first
:intoheadand optionaltail. head∈ {hf,huggingface} → Hugging Face branch. Iftailis present it must be one ofmodels/datasets/spaces(that becomes the resource sub-scope); any othertail→ exitHF_TRENDING_BAD_VAR(no notify). Notail→ pull all three resource types.head==github→ GitHub branch. Iftailis present, it's the language filter.- Any other value (no colon,
headnothf/huggingface/github) → GitHub branch, treating the whole${var}as the language filter (e.g.rust).
Then jump to the matching branch below and run it end to end.
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.
- 23d ago Changed b70f7eb03731
- 1mo ago Changed · +2 lines 4c930a5e7a5e
- 2mo ago First seen · 339 lines · 43 tokens per session scan A 737e884def0b
github-trending is a skill published in the GitHub repository aaronjmars/aeon-agent (12 stars, last pushed 14d ago), licensed MIT. It adds 43 tokens to every session and 5,539 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to github-trending, 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…
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…
agentpay-session
Cap and receipt an AI agent's spending. Open a budget-capped AgentPay session so paid tool/API calls stay under a hard USDC limit and each produces a verifiable receipt + a running ledger. Use when enforcing a spend cap across calls, tracking what an agent spent, or producing an audit trail for autonomous payments.…
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…
darwinia
Evolve trading strategies through genetic algorithms and adversarial combat. Run Darwinian selection on BTC data to discover battle-tested strategies. No API keys, no cloud.
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.