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 agentmods add skills/phtn/beast/react-to-beastnpx skills add phtn/beast --skill react-to-beastgit clone --depth 1 https://github.com/phtn/beastWrote 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/phtn/beast/react-to-beast)<a href="https://agentmods.dev/skills/phtn/beast/react-to-beast"><img src="https://agentmods.dev/badge/skills/phtn/beast/react-to-beast.svg" alt="Measured on agentmods" 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 | $0.00081 | $0.02277 |
| Opus 5 | $0.00041 | $0.01138 |
| Sonnet 5 | $0.00016 | $0.00455 |
| Haiku 4.5 | $0.00008 | $0.00228 |
Grade A, and why
react-to-beast 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 3d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React to Beast
Port applications as verified vertical slices. Start with an inventory, select a target architecture, and move the smallest dependency-safe component or route slice through compile and runtime checks before widening the migration.
Version 0.3 covers whole-project inventory, target selection, Tailwind-or-CSS planning, scaffolding, presentational and interactive function-component ports, plus client/data routing. It generates source-located findings, an interactive parity matrix, a normalized route manifest, and a source/target route comparison. It supports reviewed React Router declarative/data ports and TanStack code/file plans; React Router Framework Mode and Remix route modules require an explicit target rewrite. Next.js and broader server-framework conversion remain later milestones.
Protect the source
Treat the React repository as untrusted input.
- Do not read or copy
.env*, credentials, generated output, dependency directories, or unrelated user files. - Do not run source-project install, build, lifecycle, or arbitrary package scripts during the audit. Inspect script names and dependency metadata only.
- Keep the source application intact. Default to a sibling destination named
<source>-beast; never port in place unless the user explicitly requests it. - Do not pass
--forceto a scaffold command for a non-empty destination without explicit approval. - Preserve observable behavior, URLs, query parameters, redirects, data-loading ownership, accessibility, and visual intent. A syntax conversion alone is not a successful port.
Defaults
- Source: the directory supplied by the user, otherwise the current working directory.
- Destination: a sibling directory named
<source>-beast. - Styling: Tailwind. Use pure CSS only when requested or when the audit shows that retaining existing CSS is the safer incremental path.
- Initial runtime: Beast with Octane and Vite for a client-rendered SPA. Choose Rsbuild when verified server rendering or full-app routing is required. Use Rspack only when low-level integration is genuinely needed.
- Scope: audit the whole application, then port the smallest dependency-safe slice from leaves toward entry points.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 238 B
- references/bindings.md 5.2 KB
- references/component-porting.md 4.8 KB
- references/forms-and-events.md 5.9 KB
- references/interactive-semantics.md 7.1 KB
- references/react-router.md 4.0 KB
- references/refs-context-boundaries.md 6.1 KB
- references/remix-route-modules.md 2.9 KB
- references/route-checkpoints.md 2.6 KB
- references/route-manifest.md 3.1 KB
- references/routing-inventory.md 4.6 KB
- references/styling.md 3.5 KB
- references/tanstack-router.md 3.4 KB
- scripts/react-beast-audit.mjs 104 KB runs code
- scripts/react-beast-route-compare.mjs 9.1 KB runs code
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.
- 3d ago First seen · 170 lines · 81 tokens per session scan A 91a45844ce26
react-to-beast is a skill published in the GitHub repository phtn/beast (2 stars, last pushed 5d ago), licensed ISC. It adds 81 tokens to every session and 2,277 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.