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 agentmods add skills/aaronjmars/aeon-agent/articlenpx skills add aaronjmars/aeon-agent --skill articlegit 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/article)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/article"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/article.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.08335 |
| Opus 5 | $0.00022 | $0.04168 |
| Sonnet 5 | $0.00009 | $0.01667 |
| Haiku 4.5 | $0.00004 | $0.00834 |
Grade A, and why
article 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 3d 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 "https://api.semanticscholar.org/graph/v1/paper/search?query=TOPIC&limit=5&fields=title,authors,abstract,url,publicationDate,openAccessPdf" \ This is a copy
100% identical to article — 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 — 555 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Selector:
[angle:arg] [--visual]. The angle prefix picks the article type; append--visual(orvisual) anywhere to also generate a Replicate hero image.
- empty →
standardgeneral long-form article on an auto-selected trending topic. If the resolved topic is a single explainable mechanism, it becomes a technical explainer instead.<topic>(no recognized prefix) →standardarticle on that topic.repo:<owner/repo>→repothesis-driven article about that repo.repo:<angle>(e.g.repo:architecture) or barerepo:uses the repo frommemory/watched-repos.mdwith that angle / an auto-selected angle — this preserves repo-article's original input.lens:<topic>→lensproject-through-a-lens essay framed by that lens (e.g.lens:unix philosophy). Barelens:auto-selects the lens.--visualappended to any of the above → after the body is written, generate a Replicate hero image (optionalREPLICATE_API_TOKEN; ships text-only if absent).Examples:
"","entropy trajectory reasoning --visual","repo:aeonfun/aeon","repo:roadmap","lens:regulation wave --visual".
Today is ${today}. Write a high-quality, publication-ready article. No placeholders.
Shared preamble (every run)
- Read
memory/MEMORY.mdfor context on what topics/articles have been covered recently. - Read the last 3–7 days of
memory/logs/for recent activity — and don't re-report something already covered. - Parse
${var}intoangle+visual:- Detect a standalone
--visualorvisualtoken anywhere in${var}; if present setvisual = trueand strip that token. Otherwisevisual = false. - From what remains: if it starts with
repo:→angle = repo,arg =the rest. If it starts withlens:→angle = lens,arg =the rest. Otherwise →angle = standard,arg =the whole remaining string (empty ⇒ auto-select).
- Detect a standalone
- Dispatch to the matching angle section below. If
visual = true, run the Visual add-on after the article body is written, regardless of angle.
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.
- 3d ago First seen · 555 lines · 43 tokens per session scan A 18c9d3ab8aa8
article is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 8,335 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to article, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…