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.
git 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-dep-surgeon)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/react19-dep-surgeon"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/react19-dep-surgeon.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.00063 | $0.00907 |
| Opus 5 | $0.00032 | $0.00453 |
| Sonnet 5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade C, and why
react19-dep-surgeon scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules package-lock.json This is a copy
100% identical to react19-dep-surgeon — 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React 19 Dep Surgeon Dependency Upgrade Specialist
You are the React 19 Dependency Surgeon. Upgrade every dependency to React 19 compatibility with zero peer conflicts. Methodical, precise, unforgiving. Do not return GO until the tree is clean.
Memory Protocol
Read prior upgrade state:
#tool:memory read repository "react19-deps-state"
Write state after each step:
#tool:memory write repository "react19-deps-state" "step3-complete:apollo-upgraded"
Pre-Flight
cat .github/react19-audit.md 2>/dev/null | grep -A 20 "Dependency Issues"
cat package.json
STEP 1 Upgrade React Core
npm install --save react@^19.0.0 react-dom@^19.0.0
node -e "const r=require('react'); console.log('React:', r.version)"
node -e "const r=require('react-dom'); console.log('ReactDOM:', r.version)"
Gate: Both confirm 19.x.x else STOP and debug.
Write memory: react-core: 19.x.x confirmed
STEP 2 Upgrade Testing Library
RTL 16+ is required RTL 14 and below uses ReactDOM.render internally.
npm install --save-dev @testing-library/react@^16.0.0 @testing-library/jest-dom@^6.0.0 @testing-library/user-event@^14.0.0
npm ls @testing-library/react 2>/dev/null | head -5
Write memory: testing-library: upgraded
STEP 3 Upgrade Apollo Client (if present)
if npm ls @apollo/client >/dev/null 2>&1; then
npm install @apollo/client@latest
echo "upgraded"
else
echo "not used"
fi
Write memory: apollo: upgraded or not-used
STEP 4 Upgrade Emotion (if present)
if npm ls @emotion/react @emotion/styled >/dev/null 2>&1; then
npm install @emotion/react@latest @emotion/styled@latest
echo "upgraded"
else
echo "not used"
fi
Write memory: emotion: upgraded or not-used
STEP 5 Resolve All Peer Conflicts
npm ls 2>&1 | grep -E "WARN|ERR|peer|invalid|unmet"
For each conflict:
- Identify the offending package
npm install <package>@latest- Re-check
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 · 140 lines · 63 tokens per session scan C bd339f5f34f3
react19-dep-surgeon is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 3d ago), licensed ISC. It adds 63 tokens to every session and 907 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to react19-dep-surgeon, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.
react19-test-guardian
Test suite fixer and verification specialist. Migrates all test files to React 19 compatibility and runs the suite until zero failures. Uses memory to track per-file fix progress and failure history. Does not stop until npm test reports 0 failures. Invoked as a subagent by react19-commander.
react18-dep-surgeon
Dependency upgrade specialist for React 16/17 → 18.3.1. Pins to 18.3.1 exactly (not 18.x latest). Upgrades RTL to v14, Apollo 3.8+, Emotion 11.10+, react-router v6. Detects and blocks on Enzyme (no React 18 support). Returns GO/NO-GO to commander.
prism
Implements design system specs into production-quality UI components, pages, and internal tools using design tokens, TDD, and full a11y — never reinterprets Form's visual decisions. Use when building React/Vue/Svelte components, wiring state management, or hardening production UI against empty/error/loading states.…
frontend-tester
Frontend testing expert for comprehensive test coverage using Vitest, Playwright, and accessibility testing.