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/aeonnpx skills add aeonfun/aeon --skill aeongit 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.00147 | $0.08307 |
| Opus 5 | $0.00073 | $0.04154 |
| Sonnet 5 | $0.00029 | $0.01661 |
| Haiku 4.5 | $0.00015 | $0.00831 |
Grade E, and why
aeon scanned grade E with 4 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
"What am I doing by hand over and over that Aeon could just do?" Mode 4 turns *this* chat into a skill; Mode 8 mines *past* chats to find which chat is worth turning into one. It reads the operator's local Claude Code tr Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- **"No MCP tools available."** On the Claude harness a single unresolved `${VAR}` in `.mcp.json` disables **every** MCP server for that run, not just the broken one (`::warning::.mcp.json references secret(s) not set:` Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf aeon.git && git clone https://github.com/<owner>/<name>.git && cd <name> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
<curl / WebFetch / `./secretcurl` / `gh api` — how this skill fetches> Copies of this mod
1 near-identical copy found in the catalogue:
- aeon — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aeon
Aeon is an agent that runs on the user's own GitHub repo via Actions. A skill is a Markdown file (skills/<name>/SKILL.md); aeon.yml says which ones run and when.
Pick the mode they're asking for:
| 1 · Start | No instance yet, or set one up from scratch |
| 2 · Reschedule | Change times, cadence, or what a skill focuses on |
| 3 · Unblock | "It didn't run" / "nothing happened" |
| 4 · Chat → skill | Turn what we just did into a scheduled skill |
| 5 · Edit a skill | Change what an existing skill does |
| 6 · What to turn on | Pick skills, browse packs, install more |
| 7 · Strategy & voice | STRATEGY.md and soul/ — the north star and the tone |
| 8 · Mine history → skill | "What of my repeated work could Aeon do for me?" — surface it from past Claude Code chats |
Preflight (every mode)
-
Find the repo: current dir →
gh repo set-default→ ask. Clone it if it isn't local. -
Confirm
ghpoints at THEIR instance, before any command that writes.gh repo view --json nameWithOwner -q .nameWithOwnerIf that prints
aeonfun/aeonand they aren't working on upstream itself, stop and rungh repo set-default <owner>/<repo>.ghprefers anupstreamremote overoriginwhen no default is pinned, and every Aeon write (auth,secrets set,skills run, config pushes) is agh -R <resolved>call — so it will cheerfully put their API keys on the upstream repo and dispatch runs there. It looks like success: no error, a real run id, and the skill just never fires on their instance. -
gh auth status— everything routes throughgh. If it fails, tell them to rungh auth loginand stop. -
Use the
./aeonCLI for all config writes. It preserves comments inaeon.ymland validates. Never hand-edit the YAML — with one exception: the CLI cannot create an entry for a brand-new skill (see Mode 4 step 4).
Don't trust "disabled" for a skill you just created. The read path lists skills from disk and defaults a missing aeon.yml entry to enabled: false, so "not configured" and "disabled" look identical. One command tells them apart:
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 451 lines · 147 tokens per session scan E 3260d8d2644c
aeon is a skill published in the GitHub repository aeonfun/aeon (706 stars, last pushed 3d ago), licensed MIT. It adds 147 tokens to every session and 8,307 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it E with 4 findings (reads agent configuration directories, reads mcp configuration, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-agent
Creates and configures agent.yaml files, writes SOUL.md personality definitions, and sets up agent directory structures with skills, tools, and knowledge. Use when the user wants to configure an agent, create agent.yaml, write SOUL.md, set up agent directory structure, or customize agent settings.
manage-skills
Searches the SkillsMP registry, installs skills locally or globally, creates custom skills with SKILL.md frontmatter, and manages the skill lifecycle. Use when the user wants to find skills, add new capabilities, install a skill, browse available skills, create a custom skill, or manage the skills system.
run-agent
Configures and runs agents with different adapters including Claude, OpenAI, CrewAI, Lyzr, and GitHub Models. Supports local execution, remote git repos, and one-shot prompts. Use when the user wants to run an agent, switch LLM providers, configure adapter settings, or launch agents from git repositories.
export-agent
Converts agent definitions between frameworks — exports to Claude Code, OpenAI, CrewAI, Lyzr, and GitHub Models formats, and imports from Claude, Cursor, and CrewAI projects. Use when the user wants to convert an agent, migrate to another framework, export to LangChain/AutoGen/CrewAI, or import from existing…
get-started
Guides installation of gitagent and creation of first agent with scaffolding, configuration, and validation. Use when the user is new to gitagent, asks how to get started, wants to install gitagent, set up their first agent, or says 'how do I start?'.
semantix-guide
Troubleshoot and configure Semantix capabilities: Skills (project/custom/global/builtin priority, discovery dirs), Commands (override order, /dir:file naming), Hooks (11 events, automatic project loading, matchers, timeouts), MCP (semantix-agent.toml + .mcp.json + plugin packages, autostart), plugin packages…