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 fixgit 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/fix)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/fix"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/fix/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/fix"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/fix.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.00058 | $0.00933 |
| Opus 5 | $0.00029 | $0.00466 |
| Sonnet 5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
fix 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corrigir Testes com Falha ou Instáveis
Diagnosticar e corrigir um teste Playwright que falha ou passa intermitentemente usando uma taxonomia sistemática.
Entrada
$ARGUMENTS contém:
- Um caminho de arquivo de teste:
e2e/login.spec.ts - Um nome de teste:
"should redirect after login" - Uma descrição:
"o teste de checkout falha no CI mas passa localmente"
Passos
1. Reproduzir a Falha
Executar o teste para capturar o erro:
npx playwright test <arquivo> --reporter=list
Se o teste passar, provavelmente é instável. Executar burn-in:
npx playwright test <arquivo> --repeat-each=10 --reporter=list
Se ainda passar, tentar com workers paralelos:
npx playwright test --fully-parallel --workers=4 --repeat-each=5
2. Capturar Trace
Executar com rastreamento completo:
npx playwright test <arquivo> --trace=on --retries=0
Ler a saída do trace. Use /debug para analisar arquivos de trace se disponível.
3. Categorizar a Falha
Carregar flaky-taxonomy.md deste diretório de skill.
Todo teste com falha se enquadra em uma das quatro categorias:
| Categoria | Sintoma | Diagnóstico |
|---|---|---|
| Timing/Async | Falha intermitentemente em todo lugar | --repeat-each=20 reproduz localmente |
| Isolamento de Teste | Falha na suite, passa sozinho | --workers=1 --grep "nome do teste" passa |
| Ambiente | Falha no CI, passa localmente | Comparar capturas de tela/traces CI vs local |
| Infraestrutura | Aleatório, sem padrão | Erro referencia internos do navegador |
4. Aplicar Correção Direcionada
Timing/Async:
- Substituir
waitForTimeout()por asserções web-first - Adicionar
awaita chamadas Playwright ausentes - Aguardar respostas de rede específicas antes de asserir
- Usar
toBeVisible()antes de interagir com elementos
Isolamento de Teste:
- Remover estado mutável compartilhado entre testes
- Criar dados de teste por teste via API ou fixtures
- Usar identificadores únicos (timestamps, strings aleatórias) para dados de teste
- Verificar vazamentos de estado de banco de dados
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 · 116 lines · 58 tokens per session scan A 2ea42f8a0879
fix is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 933 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
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
reality-verification
This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
qa
Read-only automated QA sweep of a deployed stardust site on AEM Edge Delivery Services — validates routing, content fidelity vs the source capture, template conformance, rendered integrity (geometry, JS errors, broken images), visual regression vs baselines, metadata/SEO/JSON-LD, link integrity, accessibility (axe)…