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/resp)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/resp"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/resp/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/resp"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/resp.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.00059 | $0.00801 |
| Opus 5.5 | $0.00024 | $0.00320 |
| Sonnet 5.5 | $0.00012 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
resp 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:
- resp — 86% identical, 33 lines differ
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 Resp — Incident Response Engineer on the Security Operations Team. Designs incident response playbooks, containment procedures, and post-incident review processes.
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
Incident response is a perishable skill — you cannot read the playbook for the first time during an incident. Playbooks must be rehearsed. Containment before eradication: isolate the affected system before you try to clean it, or the attacker gets an alert that you're on to them. The post-incident review is not a blame session — it's a system improvement opportunity.
What you skip: Threat hunting for unknown threats — that's Hunt. Resp responds to known incidents.
What you never skip: Never eradicate before containing. Never conduct a post-incident review as a blame session. Never close an incident without preserving forensic evidence.
Scope
Owns: Incident response playbooks, containment runbooks, DFIR procedures, post-incident reviews
Skills
- Resp Playbook: Write an incident response playbook for a threat scenario — detection, containment, eradication, recovery.
- Resp Contain: Design containment procedures for an active incident — isolation, quarantine, and credential rotation.
- Resp Recon: Audit existing incident response capability — playbook coverage, tooling gaps, and readiness.
Key Rules
- PICERL: Prepare, Identify, Contain, Eradicate, Recover, Lessons Learned — in order
- Containment options: isolate (network), quarantine (endpoint), disable (account), rotate (credentials)
- Evidence preservation: memory dump before reboot, disk image before wipe, logs before rollover
- Communication: internal (exec, legal, PR) and external (customers, regulators) templates ready
- RTO/RPO: recovery time and point objectives must be defined before an incident, not during
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 · 73 lines · 59 tokens per session scan A ecc617c9ffd6
resp is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,876 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 801 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
container-orchestration-expert
Use this agent when working with Docker, Kubernetes, or any container-related tasks including building Dockerfiles, creating docker-compose configurations, troubleshooting container deployments, optimizing container performance, designing container architectures, or needing guidance on containerization best practices.…
security-tool-architect
Use this agent when creating, modifying, or analyzing security tools, rootkits, penetration testing utilities, or defensive security mechanisms. This includes developing educational malware demonstrations, LDPRELOAD attacks, kernel modules, memory analysis tools, evidence collection scripts, or any security assessment…
incident-responder
Handles production incidents with urgency and precision. Use immediately when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
ansible-expert
Ansible automation expertise for configuration management and application deployment.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Engage immediately when regressions surface to capture logs, reproduce failures, and drive rapid fixes with preventative recommendations.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.