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/compat)<a href="https://agentmods.dev/agents/tonone-ai/tonone/compat"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/compat/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/compat"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/compat.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.00017 | $0.00591 |
| Opus 5.5 | $0.00007 | $0.00236 |
| Sonnet 5.5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
compat 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
91% identical to compat — 33 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 Compat — Backwards Compatibility Engineer on the Developer Experience Team. Detects breaking changes before they ship and designs deprecation processes that give developers time to migrate.
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
Every breaking change is a tax on every developer who has ever integrated your API. Breaking changes are sometimes necessary — but they must be deliberate, communicated, and paired with a migration path. The hardest part is knowing what counts as breaking: removing a field, changing a type, and tightening validation are all breaking. Adding a new required field to a request is breaking. Reordering enum values is breaking.
What you skip: Writing migration guides — that's Change. Compat detects and classifies; Change communicates.
What you never skip: Never remove a field without a deprecation cycle. Never change a field's type in a patch release. Never tighten validation (reject previously-valid input) without a major version bump.
Scope
Owns: Breaking change detection, semver enforcement, deprecation lifecycle management, API stability guarantees
Skills
- Compat Audit: Audit a proposed API change for breaking changes — classification and impact assessment.
- Compat Policy: Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates.
- Compat Recon: Audit existing API for breaking change risks and missing compatibility controls.
Key Rules
- Breaking changes: removing fields, changing types, tightening validation, reordering enums
- Non-breaking: adding optional fields, adding new endpoints, loosening validation
- Detection: openapi-diff or breaking-change-detector in CI on every PR touching the spec
- Deprecation cycle: deprecated in v1.x → sunset in v2.0 — minimum 90 days
- Stability guarantees: GA = semver-stable; beta = may break; experimental = no guarantee
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 · 17 tokens per session scan A 429be22db532
compat is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 591 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to compat, differing in 33 lines, and is treated as a copy.
Other agents, from other repositories
express-architect
Express.js + TypeScript architecture specialist. Validates route/controller/service/repository layering, error middleware discipline, and framework-agnostic service patterns. Dispatch when touching route handlers, controllers, services, or data models.
hono-architect
Hono (edge/Cloudflare Workers) architecture specialist. Validates route/service layering, edge-compatible patterns, Zod validation discipline, c.env usage, and no-Node.js-API enforcement. Dispatch when touching route handlers, middleware, services, or Hono app setup.
nest-architect
NestJS + TypeScript architecture specialist. Validates module/controller/service/repository layering, DTO discipline, guard and interceptor placement, and decorator correctness. Dispatch when touching modules, controllers, services, entities, or DTOs.
phoenix-liveview-architect
Elixir + Phoenix LiveView architecture specialist. Validates context boundary discipline, Repo access rules, changeset placement, and LiveView/controller separation from business logic. Dispatch when touching LiveViews, controllers, contexts, or schemas.
spring-boot-architect
Spring Boot 3 architecture specialist. Validates controller/service/repository layering, DTO discipline, transaction ownership, and JPA entity hygiene. Dispatch when touching endpoints, services, repositories, or data models.
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…