compat

compat is an agent for Claude Code from jeremylongshore/tons-of-skills-marketplace. It costs 62 tokens per session (813 once invoked), scanned A, original, MIT.

An API compatibility specialist that finds changes likely to break existing integrations and plans how older interfaces should be retired.

In plain words
What is it for?
Use it for semantic-versioning audits, compatibility policies, deprecation lifecycles, and continuous-integration checks for breaking API changes.
Why use it?
It helps teams detect API drift early and give developers a deliberate path to adapt to necessary changes.

Agent for Claude Code

Written for Claude Code: background in frontmatter. Also seen: model in frontmatter.

Part of the tonone plugin — 100 agents, 9 plugins shipped together

Good fit Use it for semantic-versioning audits, compatibility policies, deprecation lifecycles, and continuous-integration checks for breaking API changes.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jeremylongshore/tons-of-skills-marketplace/compat
About the project

Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.

jeremylongshore/tons-of-skills-marketplace · 2,717 stars · on GitHub · tonsofskills.com

Install

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.

Clone the repo
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace

Made for: Claude Code.

Or install tonone, the plugin that ships this one along with the rest of its 100 agents, 9 plugins.

Wrote 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.

agentmods badge for compat

README.md
[![agentmods](https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/compat/github.svg)](https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/compat)
Your own site
<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/compat"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/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.

agentmods 80×15 button for compat

Your own site · 80×15
<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/compat"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/compat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00813
Opus 5 $0.00031 $0.00407
Sonnet 5 $0.00012 $0.00163
Haiku 4.5 $0.00006 $0.00081

Measured 9d ago against content hash fa858d8ff2ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • compat — 91% identical, 33 lines differ
plugins/ai-agency/tonone/agents/compat.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 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

Read the full file on GitHub · 73 lines

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.

  1. 9d ago First seen · 73 lines · 62 tokens per session scan A fa858d8ff2ce

Subscribe to this mod's changes

compat is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 813 once invoked, about $0.0003 per session on Opus 5. 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-09-03.