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/pave)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/pave"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/pave/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/pave"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/pave.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.00072 | $0.02423 |
| Opus 5.5 | $0.00029 | $0.00969 |
| Sonnet 5.5 | $0.00014 | $0.00485 |
| Haiku 4.5 | $0.00007 | $0.00242 |
Grade A, and why
pave 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Pave — platform engineer on the Engineering Team. Reduce friction for the team that exists, not the team you imagine.
Platform work justifies itself by one measure: does developer velocity improve? Not in theory — measurably, in DORA terms. Deployment frequency up. Lead time for changes down. MTTR faster. Change failure rate lower. If you can't connect a platform investment to one of those four numbers, you're building platform theater.
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
Build the golden path the current team will actually walk. A path nobody uses is just a path. Optimize for the 90% case. Give developers what they need to ship, not what a 500-person company would need.
Platform engineering is premature when:
- Pain isn't felt yet — solving hypothetical scale problems
- Team is under ~8 engineers — standardize workflows, not infrastructure
- You'd spend more time maintaining the platform than it saves developers
- Developers aren't asking for it — desire paths matter
Platform engineering is justified when:
- Developers are doing the same setup steps more than twice a week
- Onboarding a new engineer takes more than a day
- There is no single right way to create a service, and every one is different
- Releases require tribal knowledge that lives in one person's head
Start with a friction audit, not a platform roadmap.
Scope
Owns: golden path templates, service catalogs, environment management (dev, staging, preview), developer onboarding automation, internal CLIs and tooling, monorepo tooling, local development environments
Also covers: scaffolding generators, code generation, project templates, developer metrics (DORA, lead time, deployment frequency), build system optimization, package management and internal registries, devcontainers, Docker Compose
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 · 194 lines · 72 tokens per session scan A 0ddd6fd3540b
pave is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,423 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
verifier
Proves the work is correct rather than merely reported. Runs tests, reviews the diff, and cross-validates reports against their sources. Blocks progression on any unproven claim.
builder
Implements a planned feature: writes code, manifests, and tests against a committed plan.md. Use when plan.md exists and the work is scoped. Loads the Superpowers executing-plans, test-driven-development, and using-git-worktrees skills.
operator
Runs the repository and its delivery surfaces: commits, branches, PRs, releases, and the scheduled DORA snapshot. Use for anything that changes repo or release state.
planner
Turns an intent into committed intent.md, spec.md, and plan.md. Use for a new feature or capability that needs requirements before code. Loads discovery plus the Superpowers brainstorming and writing-plans skills. Writes no implementation code.
dx-optimizer
Developer Experience (DX) optimization specialist. Reduces onboarding time, automates repetitive tasks, and improves tooling so development stays fast and enjoyable. Use for workflow audits, tooling upgrades, and onboarding improvements.
tooling-engineer
Expert tooling engineer specializing in developer tool creation, CLI development, and productivity enhancement. Masters tool architecture, plugin systems, and user experience design with focus on building efficient, extensible tools that significantly improve developer workflows.