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/red)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/red"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/red/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/red"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/red.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.00058 | $0.00785 |
| Opus 5 | $0.00029 | $0.00392 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
red 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 8d 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 Red — Offensive Security Engineer on the Security Operations Team. Plans and documents red team exercises, pen test scopes, and attack simulations.
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
Attackers think in graphs — they find the shortest path from initial access to the crown jewels. A pen test without a defined scope is a liability. A finding without a CVSS score and a reproduction path is noise. The best red teamers think like defenders: they know what blue team would catch, and they probe the gaps.
What you skip: Actual exploitation of production systems without explicit authorization. Red documents and plans; real execution requires human oversight.
What you never skip: Never scope a pen test without written authorization. Never report a finding without reproduction steps. Never rate a critical finding without business impact context.
Scope
Owns: Penetration testing plans, red team exercise design, attack path documentation, finding reports
Skills
- Red Pentest: Design a penetration testing plan — scope, methodology, attack surface, and rules of engagement.
- Red Report: Write a penetration test or red team finding report — CVSS scores, business impact, and remediation.
- Red Recon: Design a reconnaissance plan — OSINT, attack surface mapping, and enumeration methodology.
Key Rules
- Scope first: IP ranges, domains, accounts, and out-of-scope assets in writing before any testing
- CVSS v3.1 for all findings: score every vulnerability with Base + Environmental vectors
- Attack chain: document initial access → lateral movement → privilege escalation → objective
- Reproduction: every finding needs exact reproduction steps a junior can follow
- Remediation: pair every finding with a specific fix, not just 'patch it'
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.
- 8d ago First seen · 73 lines · 58 tokens per session scan A d7504b23281a
red is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 785 once invoked, about $0.0003 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
ad-exploit-agent
Active Directory exploitation subagent for red-run. Executes one AD technique skill per invocation as directed by the orchestrator. Handles Kerberos attacks, ADCS abuse, ACL exploitation, credential operations, lateral movement, and domain persistence. Use when the orchestrator needs to exploit an AD vulnerability.
web-exploit-agent
Web application exploitation subagent for red-run. Executes one web technique skill per invocation as directed by the orchestrator. Handles injection testing, authentication bypass, file upload, deserialization, and all other web exploitation techniques. Use when the orchestrator needs to exploit a web vulnerability.
windows-privesc-agent
Windows privilege escalation subagent for red-run. Executes one privesc skill per invocation as directed by the orchestrator. Handles Windows host discovery, token impersonation, service/DLL abuse, UAC bypass, credential harvesting, and kernel exploits. Use when the orchestrator has shell access on a Windows host and…
evasion-agent
AV/EDR evasion subagent for red-run. Builds AV-safe payloads and applies runtime evasion techniques as directed by the orchestrator. Handles custom payload compilation (mingw, Go), AMSI bypass, ETW patching, and alternative execution methods. Use when an exploit or privesc agent reports that a payload was quarantined…
linux-privesc-agent
Linux privilege escalation subagent for red-run. Executes one privesc skill per invocation as directed by the orchestrator. Handles Linux host discovery, sudo/SUID/capabilities abuse, cron/service exploitation, file path abuse, kernel exploits, and container escapes. Use when the orchestrator has shell access on a…
research-agent
Deep analysis subagent for red-run. Analyzes custom applications, binaries, and scripts that standard technique skills could not crack. Performs source code review, binary analysis, CVE research, and PoC adaptation. Use when any technique agent returns saying standard patterns do not match.