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/aaronjmars/aeon-agentnpx agentmods add skills/aaronjmars/aeon-agent/pack-submitWrote 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/pack-submit)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/pack-submit"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/pack-submit/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/aaronjmars/aeon-agent/pack-submit"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/pack-submit.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.04420 |
| Opus 5.5 | $0.00011 | $0.01768 |
| Sonnet 5.5 | $0.00005 | $0.00884 |
| Haiku 4.5 | $0.00003 | $0.00442 |
Grade A, and why
pack-submit 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 23d 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 pack-submit — 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — The local skill to publish as a community pack: a skill slug (a directory name under
skills/), optionally followed by flags. Required. Examples:
token-movers— packageskills/token-movers/into a fresh public repo and submit it to the aeon registrytoken-movers --repo myorg/aeon-token-movers— override the pack repo name (defaultaeon-skill-pack-<slug>)token-movers --no-register— create and push the pack repo, but skip the registry PR againstaeonfun/aeontoken-movers --dry-run— build and validate the pack locally, write nothing to GitHub
If ${var} is empty, exit PACK_SUBMIT_NO_VAR:
./notify "pack-submit aborted: var empty — pass a skill slug e.g. \"token-movers\""
Then stop.
Today is ${today}. Your task is to take the existing skill named in ${var}, wrap it in a standalone community-pack repo (its own GitHub repo with a skills-pack.json manifest), and submit it to the aeon community registry - a PR against aeonfun/aeon that adds both surfaces the registry demands in one diff: a row in the Listed packs table in docs/community-skill-packs.md AND a matching entry in catalog/skill-packs.json. This is the inverse of install-skill: instead of pulling a community pack in, it pushes one of your own skills out for every other Aeon agent to install with bin/install-skill-pack.
What a community pack is (so you build the right thing)
A community pack is a public GitHub repo that holds one or more skills plus a skills-pack.json manifest that names and versions them. bin/install-skill-pack owner/repo reads that manifest and installs the skills. To be discoverable (listed by bin/install-skill-pack --list and the dashboard's Community Packs panel), the pack must also be registered in aeonfun/aeon's catalog/skill-packs.json + the Listed packs table in docs/community-skill-packs.md. So publishing is two moves: (a) stand up the pack repo, (b) open the registry PR. This skill does both. Full protocol: docs/community-skill-packs.md.
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.
- 23d ago Changed · -2 lines 606fe9225d78
- 1mo ago First seen · 234 lines · 27 tokens per session scan A 5e5e5a920425
pack-submit is a skill published in the GitHub repository aaronjmars/aeon-agent (12 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 4,420 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pack-submit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.
release-playbook
Use when you need the end-to-end merge -> deploy -> watch -> verdict sequence for a delivery mode, or a tool result you did not expect (refusal, park, tag exists).
release-notes-writing
Use when the stakeholder asks for release notes or a changelog - group done/released work into Added, Changed, Deprecated, Removed, Fixed and Security, in outcome language, with task references.