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/auto-mergenpx skills add aeonfun/aeon --skill auto-mergegit 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/auto-merge)<a href="https://agentmods.dev/skills/aeonfun/aeon/auto-merge"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/auto-merge.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.02298 |
| Opus 5 | $0.00010 | $0.01149 |
| Sonnet 5 | $0.00004 | $0.00460 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
auto-merge 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 5d 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.
`gh` authenticates via the workflow's GITHUB_TOKEN — no curl needed. If `gh pr merge` fails with `Resource not accessible by integration`, the workflow token lacks merge permission on that repo; log once and notify at mo Copies of this mod
1 near-identical copy found in the catalogue:
- auto-merge — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Repo (owner/repo) to target. If empty, uses every repo in memory/watched-repos.md. Env:
AUTO_MERGE_DRY_RUN=1logs intent without merging.MAX_AUTO_MERGE=Ncaps merges per run (default 3).
Merge open PRs that are fully green and pass an explicit safety policy. The policy exists because this skill runs autonomously with write access — a bug in the gate is a bug that ships to main.
Read memory/MEMORY.md and memory/watched-repos.md for repos to target. Read the last 2 days of memory/logs/ to avoid re-logging PRs already merged.
Safety policy
A PR merges only when every one of the following holds:
- Author allowlist:
author.loginis one ofdependabot[bot],renovate[bot],github-actions[bot], OR appears under a## Trusted Authorssection in memory/watched-repos.md. No allowlist → only the three bot logins are eligible. - Size cap:
additions + deletions ≤ 500. Override by applying the labelauto-merge-largeon the PR. - Base branch:
baseRefNameismainormaster. Refuse any other target. - Not a fork:
isCrossRepository == false(fork CI can be tampered with). - Not draft:
isDraft == false. - Not already queued:
autoMergeRequest == null(avoid fighting GitHub's native auto-merge if a human enabled it). - No opt-out label: none of {
do-not-merge,wip,hold,needs-review,blocked} present. - Mergeable state:
mergeStateStatus == "CLEAN"(this is stricter thanmergeable == "MERGEABLE"— CLEAN additionally requires branch-protection gates to be satisfied). - Reviews:
reviewDecision != "CHANGES_REQUESTED". - Checks: every entry in
statusCheckRolluphasconclusionin{SUCCESS, NEUTRAL, SKIPPED}. AnyFAILURE,TIMED_OUT,CANCELLED,PENDING, ornullconclusion disqualifies the PR. - Retry cap: this PR has been attempted fewer than 3 times. A PR that has hit
MERGE_FAILthree times across runs is paused — repeated failure on a CLEAN-looking PR usually means something subtle (a required check that didn't surface, branch-protection drift, token scope drift). Surface it and stop looping.
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.
- 5d ago First seen · 137 lines · 21 tokens per session scan A 6d8df520a9fd
auto-merge is a skill published in the GitHub repository aeonfun/aeon (715 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,298 once invoked, about $0.0001 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…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
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.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
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.