A test-coverage review maps the application's pages, components, API endpoints, and key user journeys, then compares them with the tests that already exist.

Use it to audit test coverage, find missing tests, and identify pages, components, endpoints, or user flows that need testing.

It shows which important parts of the application are tested and which are missing, so untested areas are easier to find.

coverage — Skill for Claude Code and Codex by ricneves-ai

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 coverage

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/coverage/github.svg)](https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/coverage)

Your own site

<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/coverage"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/coverage/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/coverage"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 860 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00860
Opus 5	$0.00028	$0.00430
Sonnet 5	$0.00011	$0.00172
Haiku 4.5	$0.00006	$0.00086

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

Security

Grade A, and why

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

engineering-team/playwright-pro/skills/coverage/SKILL.md · 101 lines

How it starts

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

Analisar Lacunas de Cobertura de Testes

Mapear todas as superfícies testáveis na aplicação e identificar o que está testado vs. o que está faltando.

Passos

1. Mapear Superfície da Aplicação

Use o subagente Explore para catalogar:

Rotas/Páginas:

Escanear definições de rota (diretório app/ do Next.js, config do React Router, Vue Router, etc.)
Listar todas as páginas voltadas ao usuário com seus caminhos

Componentes:

Identificar componentes interativos (formulários, modais, dropdowns, tabelas)
Anotar componentes com lógica de estado complexa

Endpoints de API:

Escanear arquivos de rota de API ou controllers do backend
Listar todos os endpoints com seus métodos

Fluxos de Usuário:

Identificar caminhos críticos: auth, checkout, integração, funcionalidades principais
Mapear fluxos de trabalho em múltiplas etapas

2. Mapear Testes Existentes

Escanear todos os arquivos *.spec.ts / *.spec.js:

Extrair quais páginas/rotas estão cobertas (por chamadas page.goto())
Extrair quais componentes estão testados (por uso de localizador)
Extrair quais endpoints de API são simulados ou acessados
Contar testes por área

3. Gerar Matriz de Cobertura

## Matriz de Cobertura

| Área | Rota | Testes | Status |
|---|---|---|---|
| Auth | /login | 5 | ✅ Coberto |
| Auth | /register | 0 | ❌ Faltando |
| Auth | /forgot-password | 0 | ❌ Faltando |
| Dashboard | /dashboard | 3 | ⚠️ Parcial (sem estados de erro) |
| Configurações | /settings | 0 | ❌ Faltando |
| Checkout | /checkout | 8 | ✅ Coberto |

4. Priorizar Lacunas

Classificar áreas não cobertas por impacto nos negócios:

Crítico — auth, pagamento, funcionalidades principais → testar primeiro
Alto — CRUD voltado ao usuário, pesquisa, navegação
Médio — configurações, preferências, casos extremos
Baixo — páginas estáticas, sobre, termos

5. Sugerir Plano de Testes

Para cada lacuna, recomendar:

Número de testes necessários
Qual template de templates/ usar
Esforço estimado (rápido/médio/complexo)

Read the full file on GitHub · 101 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.

9d ago First seen · 101 lines · 57 tokens per session scan A 04271505d078

Subscribe to this mod's changes

coverage is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 860 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

coverage