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/aeonfun/aeon/articlenpx skills add aeonfun/aeon --skill articlegit clone --depth 1 https://github.com/aeonfun/aeonWhat 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 2d 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" \ Copies of this mod
1 near-identical copy found in the catalogue:
- article — 100% identical, 0 lines differ
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.
- 2d ago First seen · 555 lines · 43 tokens per session scan A 18c9d3ab8aa8
article is a skill published in the GitHub repository aeonfun/aeon (706 stars, last pushed 2d 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.