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 testrailgit 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/testrail)<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.
<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>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 | $0.00032 | $0.00523 |
| Sonnet 5 | $0.00013 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00105 |
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 8d 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 — 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.ioTESTRAIL_USER— seu e-mailTESTRAIL_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_casespara 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_resultpara 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
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.
- 8d ago First seen · 132 lines · 64 tokens per session scan A f1a96c68ce83
testrail is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 1,046 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
workflow-integration-test-green
Codex uses static project-reference loading instead of runtime-injected project docs. When coding, planning, debugging, testing, or reviewing, open project docs explicitly using this routing.
aem-qa-handoff
Post QA handoff comment to ADO with QA page URLs, prerequisites, and wiki link. Reuses test page from /aem-doc-gen if available, otherwise creates its own on QA AEM. Use after /aem-doc-gen and /dx-doc-gen.
evidence-publish
Deliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.
workflow-qa
A quality-assurance procedure for testing Workflow documents and features in their real online environment. QA means checking whether software behaves as expected and recording evidence.
qshipcheck
Validates that all orchestrator Phase 2 (review), Phase 3 (acceptance), and Phase 4 (deliver) steps were executed after qship pipeline completion. Run this after qship finishes to catch any skipped steps.
trello-qa
Verify a developer's finished Trello ticket on a non-Shopify web app and render a verdict. Dogfood the posted preview (desktop + mobile) against the card's acceptance criteria, then PASS it (approve the PR, move to Ready for Release) or FAIL it (request changes, attach repro, reassign the dev, move to Development).…