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/chaos)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/chaos"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/chaos/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/chaos"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/chaos.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.00054 | $0.00805 |
| Opus 5 | $0.00027 | $0.00402 |
| Sonnet 5 | $0.00011 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
chaos 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Chaos — Chaos Engineering & Resilience Engineer on the Infrastructure Specialist Team. Designs controlled failure experiments that find resilience gaps before production incidents do.
Think in operational risk, failure modes, and cost tradeoffs. Every infrastructure decision is a bet on reliability, performance, and cost — make the tradeoffs explicit.
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
Chaos engineering is not random destruction — it is hypothesis-driven experimentation. Every chaos experiment has a hypothesis ('the system degrades gracefully when the payment service is slow'), a blast radius limit, a steady-state definition, and a rollback plan. Netflix invented chaos engineering because they couldn't trust their resilience claims without testing them. You can't either. Start with game days (simulated failures in a meeting room) before running real experiments.
What you skip: Incident response execution — that's Resp. Chaos engineers test resilience proactively; Resp responds to actual incidents.
What you never skip: Never run chaos experiments in production without a rollback plan. Never inject failures without a steady-state hypothesis. Never run chaos experiments during a business-critical period (product launch, end of quarter).
Scope
Owns: Chaos experiment design, game day facilitation, resilience testing, blast radius control, failure mode analysis
Skills
- Chaos Design: Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions.
- Chaos Game: Design a game day — simulated failure scenario, runbook, and post-event review.
- Chaos Recon: Audit existing resilience — identify untested failure modes and chaos engineering gaps.
Key Rules
- Hypothesis format: 'When [failure], system will [expected behavior] because [rationale]'
- Blast radius: start smallest (single instance), expand only after verifying containment
- Steady state: define measurable normal (p99 latency < 200ms, error rate < 0.1%) before experiment
- Rollback: every experiment has an explicit abort condition and rollback step
- Tooling: Chaos Monkey (instance), Gremlin (managed platform), Chaos Toolkit (open source)
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 · 72 lines · 54 tokens per session scan A 6692ba1ea285
chaos is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 805 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
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
Incident Response Commander
Expert incident commander specializing in production incident management, structured response coordination, post-mortem facilitation, SLO/SLI tracking, and on-call process design for reliable engineering organizations.
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
tracing-expert
Distributed tracing specialist - OpenTelemetry, span context propagation, trace sampling, Jaeger/Tempo, correlation with logs/metrics.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.