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 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/skill-article)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/skill-article"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/skill-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.1 | $0.00066 | $0.02057 |
| Opus 5 | $0.00033 | $0.01028 |
| Sonnet 5 | $0.00013 | $0.00411 |
| Haiku 4.5 | $0.00007 | $0.00206 |
Grade A, and why
skill-article scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to skill-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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Selector:
<skill-name> [--brand <handle>] [--banner].
<skill-name>→ announce that skill (must exist underskills/<skill-name>/).- empty → pick the most article-worthy skill from the last 14 days of
memory/logs/: prefer a skill that shipped recently, produced verified output, or hit a milestone. If nothing qualifies, logSKILL_ARTICLE_NO_TARGET, send no notification, and exit clean.--brand <handle>anywhere → byline/handle for the outreach footer (default: this instance's public identity fromsoul/, else the repo's org).--banneranywhere → also generate one 16:9 title banner through the Higgsfield MCP (spends credits; see Step 5). Off by default - a blank run never spends.Examples:
"aeon-update","rug-scan --brand @myproject --banner".
Today is ${today}. Write a launch article for one skill, modeled on the security-industry "skill announcement" format: the article sells the insight the skill encodes, not the file - and then gives the file away.
Shared preamble
- Read
memory/MEMORY.mdand the last 14 days ofmemory/logs/- know what this skill has actually done. - If a
soul/directory exists, readsoul/SOUL.mdandsoul/STYLE.mdfor voice. Default voice: terse, declarative, builder-wrote-this-fast. - Read the target's full
skills/<name>/SKILL.md. Every claim in the article must trace to a line in it.
Step 1 — Mine the track record (real numbers only)
Hunt for countable proof before writing a word:
memory/logs/entries under the skill's### <name>headings: runs, OK/error statuses, notable outcomes.output/files the skill produced; PRs or issues it opened (gh pr list --search).git log -- skills/<name>/for ship date and iteration history.
A real stat ("84 verified findings", "31 runs, 0 false alarms") becomes the headline. If no real count exists, the headline uses the mechanism instead. Never invent a number - a fabricated stat is the one thing that kills this format.
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 · 107 lines · 66 tokens per session scan A 7826b9d27920
skill-article is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 2,057 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to skill-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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…