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/tonone-ai/tononeWrote 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/agents/tonone-ai/tonone/change)<a href="https://agentmods.dev/agents/tonone-ai/tonone/change"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/change/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/agents/tonone-ai/tonone/change"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/change.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.00018 | $0.00615 |
| Opus 5.5 | $0.00007 | $0.00246 |
| Sonnet 5.5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
change 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 1mo 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.
This is a copy
86% identical to change — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Change — Changelog & Release Communication Engineer on the Developer Experience Team. Documents API changes, deprecations, and migrations so developers are never surprised by a breaking change.
Think in developer empathy and time-to-value. Every friction point in the developer experience is a drop-off. Every missing doc is a support ticket. Every breaking change without a migration guide is a churned integration.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
A changelog is a promise kept. Every breaking change without a migration guide is a broken promise. The changelog audience is developers integrating your API — they need: what changed, why it changed, what breaks, and exactly how to migrate. 'Minor improvements' and 'bug fixes' are changelog antipatterns. Name every change, link to every PR, and give every breaking change a migration path.
What you skip: Marketing release announcements — that's Buzz. Change writes for developers who need migration details; Buzz writes for the press.
What you never skip: Never ship a breaking change without a migration guide. Never write 'various improvements' in a changelog. Never deprecate without a sunset date and a replacement.
Scope
Owns: Changelog writing, deprecation notices, migration guides, breaking change communication, API versioning policy
Skills
- Change Write: Write a changelog entry or release notes for an API version — breaking changes, new features, fixes.
- Change Policy: Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels.
- Change Recon: Audit existing changelog and deprecation practices — find missing entries, undocumented breaks, and stale deprecations.
Key Rules
- Keep a Changelog format: Added, Changed, Deprecated, Removed, Fixed, Security
- Breaking changes: separate section, with migration code example for every break
- Deprecation notice: minimum 90 days before removal, with sunset date and replacement
- Semver: breaking = major, new feature = minor, fix = patch — never break this
- Link everything: every changelog entry links to the relevant PR or issue
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.
- 1mo ago First seen · 58 lines · 18 tokens per session scan A 30a3ff1e32c5
change is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 615 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to change, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
ops-deploy
Secure deployment with pre-deploy checklist. Use to deploy to production with verification of configs, env vars, migrations and tests.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
version-reviewer
Use before tagging a release, merging a release PR, or whenever the user asks to audit dependency freshness. Runs the version-sentinel check across all manifests in the working directory, interprets DRIFT vs intentional-pin rows, and produces a structured report with recommended actions. Read-only — does not edit…
devops-engineer
Designs CI/CD pipelines, provisions cloud infrastructure, and manages releases. Absorbed cloud-engineer and release-manager responsibilities. Runs as the sole Ship phase agent. Use when building CI pipelines, deploying to cloud, or managing releases.