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 aeonfun/aeon --skill install-skillgit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/install-skill)<a href="https://agentmods.dev/skills/aeonfun/aeon/install-skill"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/install-skill/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/install-skill"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/install-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.02264 |
| Opus 5.5 | $0.00010 | $0.00906 |
| Sonnet 5.5 | $0.00005 | $0.00453 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
install-skill 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 19d 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.
`bin/install-skill-pack` fetches the pack tarball over the network (curl to `codeload.github.com`). `curl` reaches the network fine — there is no network sandbox. If the fetch still fails: Copies of this mod
1 near-identical copy found in the catalogue:
- install-skill — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — The community pack to install:
owner/repo, optionally followed by specific skill slugs to install only a subset, and optional flags. Required. Examples:
clawhunter/clawhunter-skills— install the whole packclawhunter/clawhunter-skills clawhunter-bounties— install one skill from itrichard7463/aeon-skill-pack-claim-audit --branch develop— install from a non-default branch
If ${var} is empty, exit INSTALL_SKILL_NO_VAR:
./notify "install-skill aborted: var empty — pass a pack repo e.g. \"owner/repo\" (optionally + skill slugs)"
Then stop.
Today is ${today}. Your task is to install the community skill pack named in ${var} into this fork and ship it as a PR that auto-merges — so the skills land on main (and show up in the dashboard) with no manual step. Never commit directly to main: the change still flows through a reviewable, CI-gated PR — it just merges itself. This is the dashboard "Install" button's backend: the operator clicked it on a Community Pack card, so be fast, safe, and honest about what landed. The safety gate is real but unchanged: every skill is security-scanned and lands disabled, so nothing executes until the operator sets secrets and flips enabled: true.
How installation works (so you can explain it and trust the output)
The repo already ships a hardened installer, bin/install-skill-pack, which is the single source of truth — do not reimplement it. Given owner/repo it:
- Downloads the repo tarball and reads its
skills-pack.jsonmanifest (per-skillpath,schedule,default_enabled,secrets_required,capabilities). No manifest → it falls back to scanningskills/*/SKILL.md. - Security-scans every skill from an untrusted source via
scripts/skill-scan.sh. Sources listed inskills/security/trusted-sources.txtskip the deep scan (format checks still run). In CI there is no TTY, so a HIGH-severity finding blocks that skill unless--forceis passed — this is the safety gate, leave it on. - Copies each skill into
skills/<slug>/, then updatesaeon.yml(addedenabled: falseso nothing runs until the operator turns it on),skills.json, and records provenance inskills.lock.
Your job is to drive that script, regenerate the catalog, and wrap the result in a reviewable PR.
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.
- 19d ago Changed 4c32d7a6e321
- 20d ago Changed 424a21d34ace
- 1mo ago First seen · 120 lines · 26 tokens per session scan A 836ad1056f44
install-skill is a skill published in the GitHub repository aeonfun/aeon (782 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 2,264 once invoked, about $0.0001 per session on Opus 5.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-09-05.
Other skills, from other repositories
repo-stats-autoupdate
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
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.
git-workflow
Git branching, commits, and PR workflow following GitFlow conventions.
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.