Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aeonfun/aeonnpx agentmods add skills/aeonfun/aeon/featureWrote 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/aeonfun/aeon/feature)<a href="https://agentmods.dev/skills/aeonfun/aeon/feature"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/feature/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/aeonfun/aeon/feature"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 20 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 337 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00046 | $0.08482 |
| Opus 5.5 | $0.00018 | $0.03393 |
| Sonnet 5.5 | $0.00009 | $0.01696 |
| Haiku 4.5 | $0.00005 | $0.00848 |
Grade C, and why
feature scanned grade C with 2 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 13d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$WORK_DIR" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Fetch the canonical upstream text **straight to disk with `curl`** so the body never passes through model output — `curl -fsSL https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md -o CODE Copies of this mod
1 near-identical copy found in the catalogue:
- feature — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 616 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When the run prompt supplies a Workflow correlation ID, include the exact marker <!-- aeon-dispatch:<ID> --> in every PR body you create. This is a machine-checked chain receipt: do not alter, omit, or place it only in the final response.
${var} — Selector
target[:arg] [--fix-issues],target ∈ {watched, external, dormant}. Empty orwatched= build a feature on every watched repo (one PR each);external:<owner/repo>= one best enhancement on that external repo;dormant= revive the highest-scoring dormant repo.repair:<owner/repo#N>@<sha>is the dev-loop's bounded repair pass: update only that open PR at that exact reviewed SHA using the consumed review findings. A leadingbuild:<owner/repo | issue-url | free-text instruction>— the shape the Telegram "ship which opportunity?" force-reply sends viarepo-scanner's offer — is intercepted first and routed into the external branch on that target/instruction.--fix-issuesbiases the chosen branch toward fixing an open GitHub issue. Full grammar below.
This skill merges three repo-work modes behind one selector so no capability is lost:
| Branch | Selector | Per run | Repo source | Use it for |
|---|---|---|---|---|
| watched (§A) | empty / watched |
Iterates every watched repo, ships one PR per repo | memory/watched-repos.md |
Weekly broad sweep — keep every repo moving |
| external (§B) | external[:owner/repo[#N]] |
Single repo per run | memory/topics/repos.md catalog (or ${var} override) |
Targeted enhancement / issue fix on one repo |
| dormant (§C) | dormant[:owner/repo] |
Single dormant repo per run | memory/watched-repos.md scored by dormancy |
Reactivate a stale high-★ repo with one visible fix |
Today is ${today}. Read memory/MEMORY.md and the last 7 days of memory/logs/ before starting — and before notifying, drop anything already reported in the last ~3 days of logs.
Selector
Dev-loop repair interception — check before every normal selector. If ${var}
matches repair:<owner/repo#N>@<40-character-lowercase-sha>, this is the one
bounded repair pass authorized by a verified review receipt. Fetch that exact PR
and fail closed unless it is still open and its current head SHA exactly matches
the supplied SHA. Read the injected pr-review chain context, and require at least
one [CRITICAL] or [ISSUE] finding whose receipt matches the same target and SHA.
Checkout the PR's existing head branch; do not create a new branch or PR. Address
only those actionable findings, run the repository's relevant tests, commit and
push to the existing PR branch. If the target, SHA, receipt, branch permissions,
or requested fix is ambiguous, make no change and report the blocker. One repair
invocation is one pass: never recursively dispatch another agent or claim that a
subsequent review passed.
Telegram force-reply interception — check this immediately after the repair interception, before parsing normal selectors. If ${var} starts with build:, it is the "ship which opportunity?" force-reply that repo-scanner offers (routed here as feature with var="build:<the operator's reply>"). Strip the prefix with ${var#build:} and treat the remainder as an external build target/instruction — route it straight into the external branch (§B), reusing that branch's existing logic (do not run the watched or dormant branches for a build: value, and do not duplicate §B). Normalize the remainder into a §B target:
owner/repo→ run §B as ifexternal:owner/repo(B2 "clone that repo").- an issue URL (
https://github.com/owner/repo/issues/N) orowner/repo#N→ run §B as ifexternal:owner/repo#N(B2 "fetch that issue"). - free text like
owner/repo: add retry to the client→ run §B onowner/repo, using the trailing text as the explicit enhancement to build (see §B4's "requested enhancement" note — skip the auto-pick). - anything else with no parseable repo → run §B passing the whole remainder as the enhancement instruction; §B B2/B4 already reason about selecting and scoping a target.
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.
- 13d ago Changed ba94f00ad616
- 14d ago Changed · +1 lines 67a2ed32987d
- 15d ago Changed · +37 lines e453ea3dff0c
- 1mo ago Changed · +16 lines b71672ed11a7
- 1mo ago Changed · +8 lines b9a7d4732664
- 1mo ago First seen · 554 lines · 46 tokens per session scan C 2a02d778f165
feature is a skill published in the GitHub repository aeonfun/aeon (776 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 8,482 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, 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…
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
flowcraft-config
Author, validate, and troubleshoot complete FlowCraft configuration: deployment documents (deploy.yaml with the runtime section, inference/workspace/sandbox/tool sub-documents, core/memory contracts, and graph JSON node wiring), craft.yaml application definitions, and plugin.json manifests. Use when writing or…
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.