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/heartbeatnpx skills add aeonfun/aeon --skill heartbeatgit 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/heartbeat)<a href="https://agentmods.dev/skills/aeonfun/aeon/heartbeat"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/heartbeat.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.00040 | $0.05769 |
| Opus 5 | $0.00020 | $0.02884 |
| Sonnet 5 | $0.00008 | $0.01154 |
| Haiku 4.5 | $0.00004 | $0.00577 |
Grade A, and why
heartbeat 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 4d 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.
Applies to both branches. `curl` works — there is no network sandbox. Use **WebFetch** as a fallback for a flaky public GET. For GitHub queries (both branches use `gh pr list` / `gh issue list`), use the `gh` CLI (handle Copies of this mod
1 near-identical copy found in the catalogue:
- heartbeat — 100% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — selector. Empty (default) = the ambient fleet check — the live path a cron runs once a day; leave it empty for the scheduled run.
brief= the priority brief. See the grammar below.
Selector / ${var} grammar
- `` (empty) — Ambient check across all skills / PRs / issues, and regenerate the public status page. This is the live, scheduled path (08:00 UTC daily); its behaviour is unchanged. Leave
${var}empty for the cron. <area>(any non-empty value that is notbrief, e.g.crypto,prs) — Ambient check, with the checks focused on that area (original heartbeat focus-area behaviour).brief— Priority brief: rank the 3 things to focus on today, why now, and what moved since yesterday; send via./notify+ email.brief:<area>(e.g.brief:crypto) — Priority brief biased toward<area>.
Shared setup (every run)
Read memory/MEMORY.md and the last 2 days of memory/logs/ for context.
Parse ${var} to pick the branch:
- starts with
brief(i.e.brieforbrief:<area>) → run the Priority brief branch. Any text afterbrief:is the emphasis area. - otherwise (empty, or any other value) → run the Ambient check branch. A non-empty value is the focus area; empty runs all checks.
The two branches are mutually exclusive — run exactly one per invocation.
Ambient check (default — empty ${var}; the LIVE scheduled path)
If ${var} is set to a focus area, focus checks on that specific area.
Checks (in priority order)
P0 — Failed & stuck skills (check first)
Read memory/cron-state.json. If the file is missing or empty (e.g. a fresh fork whose scheduler hasn't written it yet), treat state as empty: report no cron-state yet for the P0 tier, skip the failure/degradation checks below, and still render the status page (every enabled skill shows not yet run). This file tracks every scheduled skill's state and quality metrics:
{
"skill-name": {
"last_dispatch": "2026-04-06T12:00:00Z",
"last_status": "dispatched|success|failed",
"last_success": "2026-04-06T12:05:00Z",
"last_failed": "2026-04-05T12:03:00Z",
"total_runs": 10,
"total_successes": 8,
"total_failures": 2,
"consecutive_failures": 0,
"success_rate": 0.80,
"last_quality_score": 4,
"last_error": "error signature text"
}
}
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.
- 4d ago First seen · 313 lines · 40 tokens per session scan A bba1bdf722ce
heartbeat is a skill published in the GitHub repository aeonfun/aeon (706 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 5,769 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…
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.
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.