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/fork-fleetnpx skills add aeonfun/aeon --skill fork-fleetgit 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.00045 | $0.08477 |
| Opus 5 | $0.00023 | $0.04238 |
| Sonnet 5 | $0.00009 | $0.01695 |
| Haiku 4.5 | $0.00005 | $0.00848 |
Grade A, and why
fork-fleet 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Every GitHub call uses `gh api`, which authenticates via `GITHUB_TOKEN` automatically — no `curl`, no `$SECRET` on the command line (so nothing for the Bash permission layer to refuse), no secrets beyond the default `GIT Copies of this mod
1 near-identical copy found in the catalogue:
- fork-fleet — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 615 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Divergence scope selector; space-separated tokens, order-independent, all optional:
- scope (
code|config|both, defaultboth) — which divergence dimension to run.repo=owner/name— override the parent repo whose forks are scanned (else auto-resolved).fork=owner/name— drill into a single fork (forcescodescope; config math needs a fleet).Empty ⇒ both dimensions over the auto-resolved parent. Examples: `` (both, all forks) ·
code·config·config repo=octo/aeon·fork=alice/aeon.
Today is ${today}. This is the fleet's divergence monitor. It answers two questions the popularity/liveness skills don't:
- Code divergence — which active forks are building real work (unique commits, new/modified skills) that's worth pulling back upstream?
- Config divergence — where does the configured fleet systematically disagree with upstream's
enabled/var/model/scheduledefaults, so the operator can flip a default the fleet has already voted on?
skill-gap ranks what's popular (top 15 by enabled count). This skill's code branch surfaces per-fork unique work; its config branch surfaces where operators disagree with defaults. If 6 of 8 configured forks enable a skill upstream defaults off, upstream is shipping the wrong default; if 5 of 8 disable a skill upstream defaults on, that skill is noise. Both are peer-learning signals.
Operating principles
- Verdict first, catalog second. The operator reads one line and knows if action is needed.
- Silent when nothing changed. Weekly cadence + a dormant/undivergent fleet = a read-once habit to kill. A clean run notifies nothing.
- Per-fork compare is one call, not three.
/compare/{owner}:main...{fork_owner}:mainreturns ahead/behind/unique commits/files in a single round-trip; the recursive git-tree returns the fork's whole file list in one call. - Substance ≠ noise. A new
skills/*/SKILL.mdis worth 100 cron-time edits inaeon.yml. Score accordingly. On the config side, an untouched template fork is not a "vote" — exclude it from divergence math.
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 · 615 lines · 45 tokens per session scan A 17249aa9122f
fork-fleet is a skill published in the GitHub repository aeonfun/aeon (706 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 8,477 once invoked, about $0.0002 per session on Opus 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-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…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
pull-requests
Guidance for creating pull requests and handling PR review comments in the Agent Framework repository. Use this when writing a PR description (filling out the PR template) or when responding to and resolving review comments on an existing PR.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.