An integration between Playwright, a browser testing tool, and TestRail, a system for managing test cases and test runs. It can move test cases into Playwright tests and send test results back to TestRail.

Use it to import TestRail cases as Playwright tests and push Playwright run results to TestRail.

Teams otherwise have to copy test steps between their test-management system and code, then update results manually. This keeps the two records linked through TestRail case IDs.

testrail — 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 testrail

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/testrail/github.svg)](https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/testrail)

Your own site

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

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

When invoked 1,046 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.00064	$0.01046
Opus 5.5	$0.00026	$0.00418
Sonnet 5.5	$0.00013	$0.00209
Haiku 4.5	$0.00006	$0.00105

Measured 1mo ago against content hash f1a96c68ce83, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testrail 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 1mo 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/testrail/SKILL.md · 132 lines

How it starts

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

Integração com TestRail

Sincronização bidirecional entre testes Playwright e o gerenciamento de testes TestRail.

Pré-requisitos

As variáveis de ambiente devem estar configuradas:

TESTRAIL_URL — ex.: https://sua-instancia.testrail.io
TESTRAIL_USER — seu e-mail
TESTRAIL_API_KEY — chave de API do TestRail

Se não estiverem configuradas, informar ao usuário como configurá-las e parar.

Capacidades

1. Importar Casos de Teste → Gerar Testes Playwright

/pw:testrail import --project <id> --suite <id>

Passos:

Chamar a ferramenta MCP testrail_get_cases para buscar os casos de teste
Para cada caso de teste:
- Ler título, pré-condições, passos, resultados esperados
- Mapear para um teste Playwright usando o template apropriado
- Incluir o ID do caso TestRail como anotação do teste: test.info().annotations.push({ type: 'testrail', description: 'C12345' })
Gerar arquivos de teste agrupados por seção
Relatório: X casos importados, Y testes gerados

2. Enviar Resultados de Testes → TestRail

/pw:testrail push --run <id>

Passos:

Executar testes Playwright com o reporter JSON:

npx playwright test --reporter=json > test-results.json

Analisar resultados: mapear cada teste para seu ID de caso TestRail (das anotações)
Chamar a ferramenta MCP testrail_add_result para cada teste:
- Aprovado → status_id: 1
- Reprovado → status_id: 5, incluir mensagem de erro
- Pulado → status_id: 2
Relatório: X resultados enviados, Y aprovados, Z reprovados

3. Criar Execução de Testes

/pw:testrail run --project <id> --name "Sprint 42 Regression"

Passos:

Chamar a ferramenta MCP testrail_add_run
Incluir todos os IDs de casos de teste encontrados nas anotações dos testes Playwright
Retornar o ID da execução para envio de resultados

4. Status de Sincronização

/pw:testrail status --project <id>

Passos:

Buscar casos de teste do TestRail
Escanear testes Playwright locais por anotações TestRail

Reportar cobertura:

Casos TestRail: 150
Testes Playwright com IDs TestRail: 120
Casos TestRail sem vínculo: 30
Testes Playwright sem IDs TestRail: 15

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

1mo ago First seen · 132 lines · 64 tokens per session scan A f1a96c68ce83

Subscribe to this mod's changes

testrail is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (117 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,046 once invoked, about $0.0003 per session on Opus 5.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.

E2E testing Project management Testing

jira-validate-production

Check that the fix a Jira issue carries is live on the PRODUCTION site and behaves as the issue asked, then close the card, or open a follow-up issue for what failed. Insert into the prompt of a run started on a batch of merged issues, or of a Jira post-deploy column rule.

decocms/studio · 67 tokens

testrail

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Integração com TestRail

Pré-requisitos

Capacidades

1. Importar Casos de Teste → Gerar Testes Playwright

2. Enviar Resultados de Testes → TestRail

3. Criar Execução de Testes

4. Status de Sincronização

What this file has done since we first saw it

Other skills, from other repositories

jira-validate-production

acceptance-criteria-gwt

pm-uat-review

retest-after-revision

evidence-publish

aem-qa-handoff