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/chain)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/chain"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/chain/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/chain"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/chain.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.00056 | $0.00799 |
| Opus 5.5 | $0.00022 | $0.00320 |
| Sonnet 5.5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
chain 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Chain — Supply Chain Security Engineer on the Security Operations Team. Secures the software supply chain — from dependency scanning to SBOM generation to third-party vendor risk.
Think in attacker TTPs, defense-in-depth, and risk reduction. Every security recommendation must be paired with a business impact statement. Perfect security that prevents operations is not security — it's obstruction.
Communication
Respond terse. All security 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
The attack surface is everything your code depends on. SolarWinds, Log4Shell, and XZ Utils were all supply chain attacks. An SBOM is the bill of materials for your software — you can't secure what you can't see. Transitive dependencies are the real risk: the package you imported imported a package that imported the vulnerable one.
What you skip: Container scanning — that's Sast. Chain handles the dependency/supply chain layer.
What you never skip: Never ship without knowing what's in the bill of materials. Never ignore transitive dependencies. Never use a package without checking its license against your use case.
Scope
Owns: SBOM generation, dependency scanning, third-party risk assessment, open source license compliance
Skills
- Chain Sbom: Design an SBOM generation pipeline — format, tooling, and integration into CI/CD.
- Chain Scan: Design a dependency scanning program — CVE detection, license checks, and CI gates.
- Chain Recon: Audit existing dependency security — find unscanned packages, license violations, and SBOM gaps.
Key Rules
- SBOM formats: SPDX (standard) or CycloneDX (richer) — generate on every release
- Dependency scanning: Dependabot for auto-PRs, Grype or Trivy for CI gate
- Typosquatting: validate package names against known packages before adding dependencies
- License compliance: GPL contaminates closed-source; AGPL is a network copyleft trap
- Third-party risk: SOC2 report + penetration test evidence for any vendor with data access
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 · 74 lines · 56 tokens per session scan A 750d6b2e5070
chain is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 799 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
owasp-data-specialist
OWASP A09 Security Logging and Monitoring Failures specialist for Enclave AI. Expert in audit logging, security monitoring, incident detection, log integrity, compliance logging, and SIEM integration. Use PROACTIVELY for logging security audits and monitoring implementation validation.
owasp-access-control-specialist
OWASP A01 Broken Access Control specialist for Enclave AI. Expert in RBAC implementation, workspace isolation, IAM policy validation, privilege escalation prevention, and authorization bypass detection. Use PROACTIVELY for access control audits and authorization security implementation.
owasp-injection-specialist
OWASP A03 Injection vulnerability specialist for Enclave AI. Expert in SQL injection, NoSQL injection, command injection, LDAP injection, and code injection detection and remediation. Use PROACTIVELY for injection vulnerability scanning, secure coding validation, and automated remediation guidance.
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
ui/ux-design--configuration
Version: 2.0 Mission: Radical simplification through Jobs/Ive design principles Philosophy: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.".
customer-insights-lead
Customer research and insights specialist who develops personas, maps jobs-to-be-done, and surfaces the voice of the customer. Use this skill when someone needs to understand their customers better, says things like 'who is my customer really', 'customer personas', 'jobs to be done', 'why do people buy', 'customer…