Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gopherguides/gopher-ai/plugin install tailwindWrote 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/commands/gopherguides/gopher-ai/migrate)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/migrate"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/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/commands/gopherguides/gopher-ai/migrate"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/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.00014 | $0.08700 |
| Opus 5.5 | $0.00006 | $0.03480 |
| Sonnet 5.5 | $0.00003 | $0.01740 |
| Haiku 4.5 | $0.00001 | $0.00870 |
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 — 803 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Tailwind CSS v3 to v4
If $ARGUMENTS is empty or not provided:
Migrate Tailwind CSS v3 configuration to v4's CSS-based configuration.
Usage: /tailwind-migrate [options]
/tailwind-migrate— migrate v3 to v4/tailwind-migrate --check— preview changes without modifying files
What it does: finds tailwind.config.js/.ts → converts theme to @theme directive → converts content paths to @source directives → updates CSS files to @import "tailwindcss" syntax → updates package.json deps → optionally removes the old config file.
Key v4 changes:
| v3 | v4 |
|---|---|
tailwind.config.js |
CSS @theme { } directive |
@tailwind base/components/utilities |
@import "tailwindcss" |
darkMode: 'class' |
@custom-variant dark (...) plus .dark { } overrides |
theme.extend.colors |
--color-* CSS variables |
Proceed with migration.
If $ARGUMENTS is provided:
Parse arguments:
--check— preview changes without modifying files--keep-config— keep old config file after migration (for reference)--backup— create backup files before modifying
Read-only Preview (--check)
When --check is present, capture the initial repository status, then follow
Steps 1-3 to analyze the v3 project and generate proposed v4 content in the
response. In Steps 4-7, describe the exact file, package, and configuration
changes that normal migration mode would make without applying them.
Do not edit files, install or remove dependencies, rename or delete configuration, or run a build that overwrites generated CSS. Skip mutation-specific questions and record the recommended old-config disposition as a preview item instead. Use the Preview Completion Criteria at the end of this workflow rather than the mutation criteria.
Without --check, perform the migration and use the Migration Completion
Criteria.
Preservation Flags
When --backup is present and --check is absent, create backups before the
first mutation. Back up every file that the migration will modify or remove,
including affected CSS, package.json, the active lockfile, PostCSS
configuration, and the v3 Tailwind configuration. Use a
.tailwind-v3.bak suffix and a numbered suffix when that path already exists.
Record every source-to-backup mapping. If any backup fails, stop before making
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 Changed f8305636f471
- 1mo ago First seen · 803 lines · 14 tokens per session scan A 7d8ca1e434d5
migrate is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 8,700 once invoked, about $0.0001 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 commands, from other repositories
/a11y-audit
Auditoría de accesibilidad WCAG 2.2 completa con escaneo de HTML/componentes. Detecta: alt text faltante, problemas de contraste, navegación por teclado, etiquetas ARIA, gestión de focus, jerarquía de encabezados, etiquetas de formularios. Genera reporte accionable con instrucciones de remediación.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.
frontend-design
Read and follow the instructions in agents/frontend-design/design-all.md. Also read all referenced files in agents/frontend-design/reference/ as needed for the task.