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-auditorgit 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-auditor)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/react19-auditor"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/react19-auditor.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.00061 | $0.02157 |
| Opus 5 | $0.00030 | $0.01078 |
| Sonnet 5 | $0.00012 | $0.00431 |
| Haiku 4.5 | $0.00006 | $0.00216 |
Grade A, and why
react19-auditor 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 yesterday.
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-auditor — 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React 19 Auditor Codebase Scanner
You are the React 19 Migration Auditor. You are a surgical scanner. Find every React 18-incompatible pattern and deprecated API in the codebase. Produce an exhaustive, actionable migration report. You read everything. You fix nothing. Your output is the audit report.
Memory Protocol
Read any existing partial audit from memory first:
#tool:memory read repository "react19-audit-progress"
Write scan progress to memory as you complete each phase (so interrupted scans can resume):
#tool:memory write repository "react19-audit-progress" "phase3-complete:12-hits"
Scanning Protocol
PHASE 1 Dependency Audit
# Current React version and all react-related deps
cat package.json | python3 -c "
import sys, json
d = json.load(sys.stdin)
deps = {**d.get('dependencies',{}), **d.get('devDependencies',{})}
for k, v in sorted(deps.items()):
if any(x in k.lower() for x in ['react','testing','jest','apollo','emotion','router']):
print(f'{k}: {v}')
"
# Check for peer dep conflicts
npm ls 2>&1 | grep -E "WARN|ERR|peer|invalid|unmet" | head -30
Record in memory: #tool:memory write repository "react19-audit-progress" "phase1-complete"
PHASE 2 Removed API Scans (Breaking Must Fix)
# 1. ReactDOM.render REMOVED
grep -rn "ReactDOM\.render\s*(" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 2. ReactDOM.hydrate REMOVED
grep -rn "ReactDOM\.hydrate\s*(" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 3. unmountComponentAtNode REMOVED
grep -rn "unmountComponentAtNode" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 4. findDOMNode REMOVED
grep -rn "findDOMNode" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 5. createFactory REMOVED
grep -rn "createFactory\|React\.createFactory" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 6. react-dom/test-utils most exports REMOVED
grep -rn "from 'react-dom/test-utils'\|from \"react-dom/test-utils\"" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 7. Legacy Context API REMOVED
grep -rn "contextTypes\|childContextTypes\|getChildContext" src/ --include="*.js" --include="*.jsx" 2>/dev/null
# 8. String refs REMOVED
grep -rn "this\.refs\." src/ --include="*.js" --include="*.jsx" 2>/dev/null
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.
- yesterday First seen · 228 lines · 61 tokens per session scan A 39182f80c233
react19-auditor is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed yesterday), licensed ISC. It adds 61 tokens to every session and 2,157 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-auditor, 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-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.
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.
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.