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.
git clone --depth 1 https://github.com/Tideshift-Labs/FathomWrote 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/commands/tideshift-labs/fathom/changelog)<a href="https://agentmods.dev/commands/tideshift-labs/fathom/changelog"><img src="https://agentmods.dev/badge/commands/tideshift-labs/fathom/changelog/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/commands/tideshift-labs/fathom/changelog"><img src="https://agentmods.dev/badge/commands/tideshift-labs/fathom/changelog.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.00000 | $0.00183 |
| Opus 5.5 | $0.00000 | $0.00073 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
changelog 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 2mo 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.
What it actually says
Review the git log since the last version tag and update CHANGELOG.md accordingly.
Steps:
- Read CHANGELOG.md to understand the current state
- Run
git logfrom the last version tag (find the latestv*tag) to HEAD, showing commit subjects - Categorize each meaningful commit under the appropriate heading (Added, Changed, Fixed, Removed) in the
## [Unreleased]section - Skip merge commits, version bump commits, and trivial changes (typos, formatting)
- Write concise, user-facing descriptions (not raw commit messages)
- Do not touch any existing versioned sections below
## [Unreleased] - Show me the diff before saving
If $ARGUMENTS is provided, treat it as additional instructions (e.g. "only include commits from the last week" or "focus on API changes").
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.
- 2mo ago First seen · 13 lines · 0 tokens per session scan A 0bfa389a592a
changelog is a command published in the GitHub repository Tideshift-Labs/Fathom (14 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 183 tokens. 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-08-30.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
release
A typical CI release creates the release, associates commits, finalizes it, and records a deploy. The sentry release create examples above show the full sequence.
release
Command "release" from getsentry/sentry-mcp, covering examples, list releases (auto-detect org), list releases in a specific org, view release details and create and finalize a release.
changelog
Generate a changelog from git commits since the last release tag.
ship
Pre-ship checklist and deployment. Run this before every production deploy.
release
Prepare and publish a semver-compliant release.