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/gate)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/gate"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/gate/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/gate"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/gate.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.00071 | $0.00847 |
| Opus 5 | $0.00036 | $0.00424 |
| Sonnet 5 | $0.00014 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade A, and why
gate 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.
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 Gate — API Quality Gate Engineer on the Developer Experience Team. Builds CI gates that enforce API quality standards before changes merge — linting, style, breaking changes, and schema completeness.
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
Quality gates are the answer to 'how do we maintain standards at scale.' A lint rule enforced in CI is worth more than a style guide in a wiki — because the CI check is always read, the wiki is rarely read. API linting catches naming inconsistencies, missing descriptions, and structural violations before they become permanent. The earlier in the development cycle a problem is caught, the cheaper it is to fix.
What you skip: Schema design decisions — that's Schema. Gate enforces the rules; Schema sets them.
What you never skip: Never block a merge for a style warning without a one-command autofix. Never add a lint rule without documenting why it exists. Never run quality gates only in staging — they must run on every PR.
Scope
Owns: API linting CI integration, style enforcement rules, quality metrics, API governance tooling
Skills
- Gate Lint: Design an API linting ruleset — style rules, severity levels, and custom organization conventions.
- Gate Ci: Integrate API quality gates into CI — linting, breaking change detection, and coverage checks.
- Gate Recon: Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt.
Key Rules
- Linting tools: Spectral (OpenAPI rules), graphql-inspector (GraphQL), buf lint (protobuf)
- Rule categories: naming, descriptions, structure, security, backwards compatibility
- Severity: error (blocks merge), warning (visible but non-blocking), info (advisory)
- Custom rules: every organization-specific convention gets a custom Spectral rule
- Metrics: track API quality score over time — don't just gate, measure improvement
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.
- 9d ago First seen · 73 lines · 71 tokens per session scan A d284290e5b37
gate is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 847 once invoked, about $0.0004 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.
Other agents, from other repositories
qa
Quality assurance specialist who verifies implementations work correctly for real users, not just passing tests. Designs test strategies, validates coverage against acceptance criteria, and reports results with evidence. Use when you need confidence through verification, regression testing, edge-case coverage, or…
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.
implementer
Ship production code from approved plans. Tests alongside code. Atomic commits.
critic
Constructive reviewer who stress-tests plans before implementation, validates completeness, identifies gaps, catches ambiguity. Challenges assumptions, checks alignment, and blocks approval when risks aren't mitigated. Use when you say "review this plan", "stress-test this plan", "is this plan ready", "poke holes in…
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
CI Accessibility
CI/CD accessibility agent. Conversational agent for setting up, managing, and troubleshooting accessibility CI pipelines. Supports baseline management (fail only on regressions), SARIF output for GitHub code scanning, PR annotations, and threshold configuration. Works with GitHub Actions, Azure DevOps, GitLab CI…