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 migrategit 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/migrate)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/migrate"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/migrate/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/migrate"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/migrate.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.01156 |
| Opus 5.5 | $0.00023 | $0.00462 |
| Sonnet 5.5 | $0.00012 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
migrate 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrar para o Playwright
Migração interativa do Cypress ou Selenium para o Playwright com conversão arquivo por arquivo.
Entrada
$ARGUMENTS pode ser:
"from cypress"— migrar suite de testes Cypress"from selenium"— migrar testes Selenium/WebDriver- Um caminho de arquivo: converter um arquivo de teste específico
- Vazio: detectar automaticamente o framework de origem
Passos
1. Detectar o Framework de Origem
Use o subagente Explore para escanear:
- Diretório
cypress/oucypress.config.ts→ Cypress selenium,webdrivernas dependências dopackage.json→ Selenium- Arquivos
.pycom imports deselenium→ Selenium (Python)
2. Avaliar o Escopo da Migração
Contar arquivos e categorizar:
Avaliação de Migração:
- Total de arquivos de teste: X
- Comandos customizados Cypress: Y
- Fixtures Cypress: Z
- Esforço estimado: [pequeno|médio|grande]
| Tamanho | Arquivos | Abordagem |
|---|---|---|
| Pequeno (1-10) | Converter sequencialmente | Conversão direta |
| Médio (11-30) | Em lotes de 5 | Usar subagentes |
| Grande (31+) | Usar /batch |
Conversão paralela com /batch |
3. Configurar Playwright (Se Não Estiver Presente)
Executar /pw:init primeiro se o Playwright não estiver configurado.
4. Converter Arquivos
Para cada arquivo, aplicar o mapeamento apropriado:
Cypress → Playwright
Carregar cypress-mapping.md para referência completa.
Traduções principais:
cy.visit(url) → page.goto(url)
cy.get(selector) → page.locator(selector) ou page.getByRole(...)
cy.contains(text) → page.getByText(text)
cy.find(selector) → locator.locator(selector)
cy.click() → locator.click()
cy.type(text) → locator.fill(text)
cy.should('be.visible') → expect(locator).toBeVisible()
cy.should('have.text') → expect(locator).toHaveText(text)
cy.intercept() → page.route()
cy.wait('@alias') → page.waitForResponse()
cy.fixture() → import JSON ou arquivo de dados de teste
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 · 138 lines · 58 tokens per session scan A b93433413c63
migrate is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (117 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,156 once invoked, about $0.0002 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.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.