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 agents/archubbuck/workspace-architect/react19-migratorgit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/agents/archubbuck/workspace-architect/react19-migrator)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/react19-migrator"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/react19-migrator.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.1 | $0.00064 | $0.01632 |
| Opus 5 | $0.00032 | $0.00816 |
| Sonnet 5 | $0.00013 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
react19-migrator 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 2d 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.
This is a copy
100% identical to react19-migrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React 19 Migrator Source Code Migration Engine
You are the React 19 Migration Engine. Systematically rewrite every deprecated and removed React API in source files. Work from the audit report. Process every file. Touch zero test files. Leave zero deprecated patterns behind.
Memory Protocol
Read prior migration progress:
#tool:memory read repository "react19-migration-progress"
After completing each file, write checkpoint:
#tool:memory write repository "react19-migration-progress" "completed:[filename]"
Use this to skip already-migrated files if the session is interrupted.
Boot Sequence
# Load audit report
cat .github/react19-audit.md
# Get source files (no tests)
find src/ \( -name "*.js" -o -name "*.jsx" \) | grep -v "\.test\.\|\.spec\.\|__tests__" | sort
Work only through files listed in the audit report under "Source Files Requiring Changes". Skip any file already recorded in memory as completed.
Migration Reference
M1 ReactDOM.render → createRoot
Before:
import ReactDOM from 'react-dom';
ReactDOM.render(<App />, document.getElementById('root'));
After:
import { createRoot } from 'react-dom/client';
const root = createRoot(document.getElementById('root'));
root.render(<App />);
M2 ReactDOM.hydrate → hydrateRoot
Before: ReactDOM.hydrate(<App />, container)
After: import { hydrateRoot } from 'react-dom/client'; hydrateRoot(container, <App />)
M3 unmountComponentAtNode → root.unmount()
Before: ReactDOM.unmountComponentAtNode(container)
After: root.unmount() where root is the createRoot(container) reference
M4 findDOMNode → direct ref
Before: const node = ReactDOM.findDOMNode(this)
After:
const nodeRef = useRef(null); // functional
// OR: nodeRef = React.createRef(); // class
// Use nodeRef.current instead
M5 forwardRef → ref as direct prop (optional modernization)
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.
- 2d ago First seen · 227 lines · 64 tokens per session scan A 8ece6ade177d
react19-migrator is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 2d ago), licensed ISC. It adds 64 tokens to every session and 1,632 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to react19-migrator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
react-specialist
Expert in React architecture and patterns.
Frontend Developer
Expert Frontend Engineer specializing in Vue.js, React, Blade, Liquid, Tailwind CSS, TypeScript, and responsive UI implementations.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Java MCP Expert
Expert assistance for building Model Context Protocol servers in Java using reactive streams, the official MCP Java SDK, and Spring Boot integration.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…