stress-test

stress-test is a skill for Claude Code, Codex from ricneves-ai/flowgrammers-skills. It costs 21 tokens per session (2,136 once invoked), scanned A, original, MIT.

A framework for testing whether a business assumption is likely to hold up. It covers assumptions such as market size, revenue forecasts, hiring speed, and customer retention.

In plain words
What is it for?
Use it to examine a business claim, identify how it could fail, and calibrate projections against possible downside cases.
Why use it?
It exposes optimistic or weak assumptions before they lead to bad plans or investment decisions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to examine a business claim, identify how it could fail, and calibrate projections against possible downside cases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ricneves-ai/flowgrammers-skills/stress-test
Install

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.

Any agent
npx skills add ricneves-ai/flowgrammers-skills --skill stress-test
Clone the repo
git clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for stress-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/stress-test/github.svg)](https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/stress-test)
Your own site
<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/stress-test"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/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.

agentmods 80×15 button for stress-test

Your own site · 80×15
<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/stress-test"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/stress-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,136 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.02136
Opus 5 $0.00010 $0.01068
Sonnet 5 $0.00004 $0.00427
Haiku 4.5 $0.00002 $0.00214

Measured 13d ago against content hash 18c14f560a7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

stress-test 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 13d 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.

c-level-advisor/executive-mentor/skills/stress-test/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/em:stress-test — Teste de Estresse de Premissas de Negócio

Comando: /em:stress-test <assumption>

Pegue qualquer premissa de negócio e quebre-a antes que o mercado o faça. Projeções de receita. Tamanho de mercado. Fosso competitivo. Velocidade de contratação. Retenção de clientes.


Por que a Maioria das Premissas Está Errada

Fundadores são otimistas por natureza. Isso é uma característica — você precisa de otimismo para começar algo do zero. Mas se torna uma desvantagem quando as premissas nos modelos de negócio são infladas pelo mesmo otimismo que o fez começar.

As premissas mais perigosas são aquelas com as quais todos concordam.

Quando o time inteiro acredita que o mercado de R$250M é real, quando cada conversa com investidor vai bem então você assume que a rodada fechará, quando seu modelo mostra R$10M ARR em dezembro e ninguém questiona — é quando você está mais exposto.

Teste de estresse não é pessimismo. É calibração.


A Metodologia de Teste de Estresse

Passo 1: Isole a Premissa

Declare explicitamente. Não "nosso mercado é grande" mas "o mercado total endereçável para software de gestão de despesas B2B para PMEs brasileiras é R$11,5B."

Quanto mais específica a premissa, mais testável ela é. Premissas vagas são infalsificáveis — e portanto inúteis.

Tipos comuns de premissas:

  • Tamanho de mercado — TAM, SAM, SOM; taxa de crescimento; segmentos de clientes
  • Comportamento do cliente — disposição para pagar, churn, expansão, indicações
  • Modelo de receita — taxas de conversão, tamanho do negócio, ciclo de vendas, CAC
  • Posição competitiva — durabilidade do fosso, velocidade de resposta do concorrente, custo de troca
  • Execução — velocidade do time, cronograma de contratação, cronograma de produto, escalabilidade operacional
  • Macro — ambiente regulatório, condições econômicas, disponibilidade de tecnologia

Passo 2: Encontre as Evidências Contrárias

Para cada premissa, busque ativamente evidências de que está errada.

Read the full file on GitHub · 205 lines

Changes

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.

  1. 13d ago First seen · 205 lines · 21 tokens per session scan A 18c14f560a7b

Subscribe to this mod's changes

stress-test is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 2,136 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens