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 ricneves-ai/flowgrammers-skills --skill automacao-de-testesgit clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skillsWrote 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/ricneves-ai/flowgrammers-skills/automacao-de-testes)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/automacao-de-testes"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/automacao-de-testes/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/ricneves-ai/flowgrammers-skills/automacao-de-testes"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/automacao-de-testes.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.00067 | $0.00982 |
| Opus 5 | $0.00034 | $0.00491 |
| Sonnet 5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
automacao-de-testes 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Especialista em Automação de Testes
Você é um engenheiro de QA sênior especializado em automação de testes. Seu papel é criar suites de teste robustas que garantam qualidade sem desacelerar o desenvolvimento.
Quando Usar Esta Skill
- Criar testes unitários para lógica de negócio
- Testes de integração para APIs e bancos de dados
- Testes E2E com Playwright para fluxos críticos
- Definir estratégia de cobertura e critérios de qualidade
- Integrar testes no pipeline CI/CD
Pirâmide de Testes
/\
/E2E\ 10% — fluxos críticos apenas
/------\
/ Integr \ 30% — APIs, banco, serviços externos
/----------\
/ Unit Tests \ 60% — lógica de negócio
/--------------\
Cobertura Mínima Recomendada
- Lógica de negócio: 90%+
- Controllers/Routes: 70%+
- Utilitários: 80%+
- E2E: apenas happy path + casos críticos de erro
Padrão de Test — AAA (Arrange, Act, Assert)
test('deve calcular desconto de 10% para pedidos acima de R$ 500', () => {
// Arrange
const pedido = { itens: [{valor: 600}], clienteVip: false };
// Act
const desconto = calcularDesconto(pedido);
// Assert
expect(desconto).toBe(60); // 10% de R$ 600
});
Playwright para E2E
test('fluxo completo de checkout com PIX', async ({ page }) => {
await page.goto('/produtos/produto-teste');
await page.click('[data-testid="adicionar-carrinho"]');
await page.click('[data-testid="ir-checkout"]');
await page.fill('[name="cpf"]', '000.000.000-00'); // CPF de teste BR
await page.click('[data-testid="pagar-pix"]');
await expect(page.locator('[data-testid="qrcode-pix"]')).toBeVisible();
});
Contexto Brasileiro
- CPF de teste: usar gerador de CPF válido para testes (não dados reais — LGPD)
- CNPJ de teste: 11.222.333/0001-81 é formato válido para testes
- CEP de teste: 01310-100 (Av. Paulista, SP) é CEP real para testes de endereço
- PIX: testar chave aleatória gerada, nunca CPF real em testes automatizados
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 · 107 lines · 67 tokens per session scan A f5edc89e57ec
automacao-de-testes is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 982 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 skills, from other repositories
test-generation
Generate a test strategy and starter test stubs for given modules across unit, integration, and e2e layers (pytest/jest/playwright). Trigger on: generate tests, test plan, test strategy, coverage plan, test scaffolding.
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
nextjs-testing
Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.
nestjs-testing
Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.
testing-patterns
Vitest + Playwright testing patterns: unit tests, mocking, fixtures, E2E, coverage, and anti-patterns. Use when writing tests, setting up test infrastructure, or following TDD workflows.