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.
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/jeremylongshore/tons-of-skills-marketplaceWrote 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/jeremylongshore/tons-of-skills-marketplace/compat)<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.
<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>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.00062 | $0.00813 |
| Opus 5.5 | $0.00025 | $0.00325 |
| Sonnet 5.5 | $0.00012 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- compat — 91% identical, 33 lines differ
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
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 · 73 lines · 62 tokens per session scan A fa858d8ff2ce
compat is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 813 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
ai-architect
Specializes in architecting AI-powered applications on Vercel — choosing between AI SDK patterns, configuring providers, building agents, setting up durable workflows, and integrating MCP servers. Use when designing AI features, building chatbots, or creating agentic applications.
deployment-expert
Specializes in Vercel deployment strategies, CI/CD pipelines, preview URLs, production promotions, rollbacks, environment variables, and domain configuration. Use when troubleshooting deployments, setting up CI/CD, or optimizing the deploy pipeline.
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use proactively for API docs, configuration references, or complete technical specifications.
creo-stripe-cli
Stripe CLI and MCP expert for payments, subscriptions, customers, products, webhooks, and billing.