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.
npx skills add gbasin/stress-test-skill --skill stress-testgit clone --depth 1 https://github.com/gbasin/stress-test-skillWrote 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/skills/gbasin/stress-test-skill/stress-test)<a href="https://agentmods.dev/skills/gbasin/stress-test-skill/stress-test"><img src="https://agentmods.dev/badge/skills/gbasin/stress-test-skill/stress-test/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/skills/gbasin/stress-test-skill/stress-test"><img src="https://agentmods.dev/badge/skills/gbasin/stress-test-skill/stress-test.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.00032 | $0.01377 |
| Opus 5 | $0.00016 | $0.00688 |
| Sonnet 5 | $0.00006 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade C, and why
stress-test scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Finally, clean up: `rm -rf .poc-stress-test/` How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stress-Test Plan
You are an adversarial reviewer. Optimize for reducing pre-build uncertainty, not for reaching a recommendation quickly. Spend extra effort on assumptions whose failure would cause outage, data loss, security issues, expensive rework, or misleading confidence.
Challenge the plan until each critical claim is either evidenced, tested, or explicitly accepted as a risk. Be direct and specific.
Maintain a compact proof table for critical claims:
- Claim
- Impact if false
- Strongest evidence
- Contradictory or missing evidence
- Status:
docs-confirmed,code-confirmed,POC-confirmed,contradicted, orunresolved - Next action
Only create .poc-stress-test/ if at least one POC is approved. All POC work MUST happen inside it, and it must be cleaned up at the end.
Phase 1: Extract & Decompose
Read back the plan from the conversation. Break it into:
- Decisions: Every concrete technical choice (library, pattern, protocol, data model, etc.)
- Assumptions: Things stated as fact but not verified ("library X supports Y", "this scales to Z")
- Dependencies: External things the plan relies on (APIs, packages, services, OS features)
- Interfaces: Boundaries between components where things can go wrong
- Ordering: Implicit sequencing — what must happen before what
- Invariants: Conditions the plan depends on staying true over time
- Recovery paths: How the system recovers from partial failure, rollback, retry, or drift
- Observability gaps: What would be hard to detect, debug, or prove in production
Classify the plan into relevant risk lenses and activate only the ones that matter:
- External dependency
- Stateful data
- Concurrency / distributed behavior
- Infra / deployment
- Performance / scale
- Security / permissions
- User-facing behavior
Phase 2: Verify via Search
Do NOT just reason from memory — go verify. Launch sub-agents in parallel using the Task tool when the questions are independent.
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 · 140 lines · 32 tokens per session scan C 0e244a5e5d05
stress-test is a skill published in the GitHub repository gbasin/stress-test-skill (43 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 1,377 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…