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 submit-hookgit 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/submit-hook)<a href="https://agentmods.dev/skills/aeonfun/aeon/submit-hook"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/submit-hook/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/submit-hook"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/submit-hook.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.00039 | $0.01402 |
| Opus 5 | $0.00019 | $0.00701 |
| Sonnet 5 | $0.00008 | $0.00280 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
submit-hook 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} - a hook address (
0x...) to submit. Empty means the most recent live mainnet deploy inmemory/state/hook-deploys.json.
Today is ${today}. This skill takes a hook this instance already deployed and lists it on the public registry aeonfun/univ4-hooks (the source behind the aeon hook marketplace). It does the formatting the registry expects, then opens a PR. The flags and callbacks are decoded from the address by the registry, so this skill only supplies the address, the chain, and the human-readable listing.
The mechanics (clone, write the entry, regenerate the registry, open the PR, fall back to an issue when there is no push access) live in skills/submit-hook/submit-univ4.py, so all GitHub egress stays inside that helper.
What lists, and what does not
- Only live mainnet deploys. A dry-run or a testnet deploy is never submitted (the registry lists real, verifiable hooks). Skip with
SUBMIT_HOOK_SKIP. - Only registry-supported chains. The registry's
chains.jsoncoversethereum base robinhood monad bnb arbitrum unichain. A deploy on any other chain is skipped (SUBMIT_HOOK_UNSUPPORTED_CHAIN); note it and stop. - Idempotent. The helper skips if the address (any chain) or the slug is already listed, so re-running is safe.
Steps
-
Pick the deploy. Read
memory/state/hook-deploys.json(a list of deploy records). If${var}is a0x...address, select the record whosehookAddressmatches it; else select the most recent record withnetwork: "mainnet". No matching record means notify and exitSUBMIT_HOOK_NONE. -
Gate it. If the record's
networkis notmainnet, exitSUBMIT_HOOK_SKIP. If itschainis not one ofethereum base robinhood monad bnb arbitrum unichain, exitSUBMIT_HOOK_UNSUPPORTED_CHAIN(the registry cannot list it yet). Confirmint(hookAddress,16) & 0x3FFF == int(flags,16); if not, the record is inconsistent, so notify and exitSUBMIT_HOOK_BAD_RECORD. -
Name it. Derive a PascalCase contract-style
namefrom the record'sbrief/feature (a market-hours gate becomesMarketHoursGate). This is the marketplace title and thehooks/<slug>.jsonfilename.
What ships with it
1 file 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.
- yesterday First seen · 73 lines · 39 tokens per session scan A 669cda6057ec
submit-hook is a skill published in the GitHub repository aeonfun/aeon (722 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,402 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.
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.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
guide-recap
Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate release notes, announcements, social media posts, or recap summaries from guide updates.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.