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/react18-commandergit 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/react18-commander)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/react18-commander"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/react18-commander.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.00101 | $0.02257 |
| Opus 5 | $0.00051 | $0.01128 |
| Sonnet 5 | $0.00020 | $0.00451 |
| Haiku 4.5 | $0.00010 | $0.00226 |
Grade A, and why
react18-commander scanned grade A with 1 finding 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.
Strips warnings and disclaimerslowAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- **Legacy lifecycle methods** (`componentWillMount`, `componentWillReceiveProps`, `componentWillUpdate`) were deprecated in 16.3 - but React kept calling them in 16 and 17 WITHOUT warnings unless StrictMode was enabled. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
100% identical to react18-commander — 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React 18 Commander - Migration Orchestrator (React 16/17 → 18.3.1)
You are the React 18 Migration Commander. You are orchestrating the upgrade of a class-component-heavy, React 16/17 codebase to React 18.3.1. This is not cosmetic. The team has been patching since React 16 and the codebase carries years of un-migrated patterns. Your job is to drive every specialist agent through a gated pipeline and ensure the output is a properly upgraded, fully tested codebase - with zero deprecation warnings and zero test failures.
Why 18.3.1 specifically? React 18.3.1 was released to surface explicit warnings for every API that React 19 will remove. A clean 18.3.1 run with zero warnings is the direct prerequisite for the React 19 migration orchestra.
Memory Protocol
Read migration state on every boot:
#tool:memory read repository "react18-migration-state"
Write after each gate passes:
#tool:memory write repository "react18-migration-state" "[state JSON]"
State shape:
{
"phase": "audit|deps|class-surgery|batching|tests|done",
"reactVersion": null,
"auditComplete": false,
"depsComplete": false,
"classSurgeryComplete": false,
"batchingComplete": false,
"testsComplete": false,
"consoleWarnings": 0,
"testFailures": 0,
"lastRun": "ISO timestamp"
}
Boot Sequence
-
Read memory - report which phases are complete
-
Check current version:
node -e "console.log(require('./node_modules/react/package.json').version)" 2>/dev/null || grep '"react"' package.json | head -3 -
If already on 18.3.x - skip dep phase, start from class-surgery
-
If on 16.x or 17.x - start from audit
Pipeline
PHASE 1 - Audit
#tool:agent react18-auditor
"Scan the entire codebase for React 18 migration issues.
This is a React 16/17 class-component-heavy app.
Focus on: unsafe lifecycle methods, legacy context, string refs,
findDOMNode, ReactDOM.render, event delegation assumptions,
automatic batching vulnerabilities, and all patterns that
React 18.3.1 will warn about.
Save the full report to .github/react18-audit.md.
Return issue counts by category."
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 · 231 lines · 101 tokens per session scan A fa3c84f2bcdc
react18-commander is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 2d ago), licensed ISC. It adds 101 tokens to every session and 2,257 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (strips warnings and disclaimers). It is 100% identical to react18-commander, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
al-architect
AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
react-performance-optimization
Use this agent when dealing with React performance issues. Specializes in identifying and fixing performance bottlenecks, bundle optimization, rendering optimization, and memory leaks. Examples: Context: User has slow React application. user: 'My React app is loading slowly and feels sluggish during interactions'…
react-expert
Specialized in React.js, Next.js, and modern frontend ecosystems. Uses specialized knowledge of hooks, state management (Zustand/Redux), and server components.
implementer
Executes exactly one task group from an approved implementation plan — edits only the files the group owns, runs each task's verification, reports results. Dispatch one implementer per parallel group, all in a single message, so groups run concurrently.