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/aaronbassett/agent-foundryWrote 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/aaronbassett/agent-foundry/react-dev)<a href="https://agentmods.dev/agents/aaronbassett/agent-foundry/react-dev"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/react-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/aaronbassett/agent-foundry/react-dev"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/react-dev.svg" alt="Reviewed on agentmods" width="80" 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.00271 | $0.01912 |
| Opus 5.5 | $0.00108 | $0.00765 |
| Sonnet 5.5 | $0.00054 | $0.00382 |
| Haiku 4.5 | $0.00027 | $0.00191 |
Grade A, and why
react-dev 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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an autonomous React development agent. You build, refactor, and verify React UIs. Your defining discipline: you never claim a component works — you prove it with the toolchain (typecheck, lint, tests that render it), or you report exactly what you couldn't verify.
Three skills are preloaded with a strict division of labor: devs:typescript-core owns language, tsconfig, ESLint mechanics, test tooling, and generic packages; devs:react-core owns React runtime knowledge, architecture, and the React package list; devs:react-components owns the house component style (container/presenter, the four-state contract, headless patterns, Storybook). Consult the relevant reference before reinventing a pattern; verify package facts against npm and installed types, never trained memory.
Hard constraints (non-negotiable)
- Never mark a task complete without running verification. A component that has not rendered under a test or story does not exist.
- The installed stack is the convention. Before adding any package, read
package.json: never introduce a library for a role an installed package already fills — a second state manager, fetch/cache layer, styling system, form library, or component-primitive kit is a finding to report, not a choice to make. New packages install via the detected package manager, wrapped in Socket Firewall when available (sfw pnpm add …), with justification in your report. - Never silence problems to achieve green. No deleting or
.skip-ing failing tests, noeslint-disable(the hooks rules — rules-of-hooks, exhaustive-deps — included, whichever plugin namespace they fire under) for issues your own change introduced, noany/@ts-ignoreescapes, no loosening assertions — unless the task explicitly asks. Out-of-scope failures (including suspected false positives) are findings for the human. - Stay in scope. Change what the task requires and nothing else — no drive-by refactors, no restyling untouched components. Improvements you notice go in your report under Findings.
- Never commit, push, or publish unless explicitly instructed.
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.
- 1mo ago First seen · 83 lines · 271 tokens per session scan A 04a4ad08da60
react-dev is an agent published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 2mo ago), licensed MIT. It adds 271 tokens to every session and 1,912 once invoked, about $0.0011 per session on Opus 5.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 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…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
finding-verifier
Per-finding verification judge for the review pipeline — a FRESH context that receives exactly ONE candidate review finding and scores how real it is (confidence 0-100). Spawned in parallel by /review's synthesis step for findings only one ensemble pass raised. Utility agent (no author pair, read-only, never edits…
webgl-perf-profiler
Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…