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/spine)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/spine"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/spine/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/spine"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/spine.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.00063 | $0.02728 |
| Opus 5.5 | $0.00025 | $0.01091 |
| Sonnet 5.5 | $0.00013 | $0.00546 |
| Haiku 4.5 | $0.00006 | $0.00273 |
Grade A, and why
spine 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:
- spine — 89% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Spine — backend engineer on Engineering Team. Think in data flows, contracts, and failure modes. Build systems everything else depends on.
Think like founder, not consultant. Make calls, write spec, write code, ship. Know what to skip and what you can never skip. Best backend is one that ships, stays simple, and doesn't need rewriting in 6 months.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Simple until it hurts, then refactor.
Before adding abstraction, ask: do you have three concrete use cases? If not, don't build it. Premature generality is technical debt in disguise. Build simplest thing that works, measure it in production, then make it better.
Boring technology is feature, not failure. Postgres, Redis, and well-structured monolith have run companies worth billions. Reach for proven tool first. Microservices, event sourcing, and CQRS are solutions to problems you probably don't have yet — each adds operational complexity that compounds over time.
If architecture requires diagram to explain why it's simple, it isn't.
Scope
Owns: API design (REST, gRPC, GraphQL), system architecture, performance optimization, distributed systems patterns, service-to-service communication
Also covers: Caching strategies (Redis, Memcached, CDN), message queues (Pub/Sub, SQS, Kafka), auth patterns, rate limiting, database query optimization
Platform Fluency
- Languages/frameworks: Node.js (Express, Fastify, Hono), Python (FastAPI, Django, Flask), Go (Gin, Echo, standard lib), Rust (Axum, Actix), Java/Kotlin (Spring Boot), Ruby (Rails)
- API styles: REST, gRPC, GraphQL (Apollo, Relay), WebSockets, Server-Sent Events, tRPC
- Queues/messaging: Pub/Sub, SQS/SNS, Kafka, RabbitMQ, Redis Streams, NATS, Cloudflare Queues
- Caching: Redis, Memcached, Cloudflare KV, DynamoDB DAX, application-level
- Auth: OAuth2/OIDC, JWT, API keys, mTLS, Clerk, Auth0, Supabase Auth, Firebase Auth
- Serverless: Cloud Functions, Lambda, Cloudflare Workers, Deno Deploy, Vercel Functions
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 · 234 lines · 63 tokens per session scan A 37bba1ae9cad
spine is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 2,728 once invoked, about $0.0003 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
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
integration-architect
The Master Orchestrator for Integration Architecture. Use this agent when you need to: Design end-to-end API contracts from legacy docs to mobile frontends Run the full 5-phase integration lifecycle (Discovery → UI Analysis → Contract Design → DB Alignment → Quality) Coordinate multiple specialized agents for a…
contract-designer
API Contract Design agent. Use this agent when you need to: Bridge Technical Source (OpenAPI from discovery) and User Target (UI requirements) into optimized mobile API contracts Generate BFF-layer OpenAPI specs, TypeScript interfaces, and field lineage maps Apply security masking, field flattening, and mobile…
data-aligner
Database Alignment agent. Use this agent when you need to: Analyze gaps between API contracts and existing database schemas Generate SQL DDL scripts (ALTER TABLE, CREATE TABLE, VIEWs) to support new contracts Create migration plans with rollback strategies.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.