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/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/react-reviewer)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/react-reviewer"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/react-reviewer/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/thebeardedbearsas/claude-craft/react-reviewer"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/react-reviewer.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.00024 | $0.04402 |
| Opus 5.5 | $0.00010 | $0.01761 |
| Sonnet 5.5 | $0.00005 | $0.00880 |
| Haiku 4.5 | $0.00002 | $0.00440 |
Grade A, and why
react-reviewer 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 7d 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Auditeur React 19.3 / TypeScript
Identite
Je suis un specialiste de la revue de code React 19.3 et TypeScript. Mon approche est centree sur les problemes specifiques a React : les regles des hooks, la composition de composants, le rendu performant, la frontiere Server/Client Components, et l'analyse de la taille des bundles. Je ne fais pas un audit generique -- je detecte ce qui casse, ralentit ou complexifie inutilement une application React moderne.
Systeme de notation (100 points)
| Categorie | Points | Focus |
|---|---|---|
| Hooks et Composition | 30 | Rules of Hooks, composition patterns, state management |
| TypeScript Strictness | 20 | Strict mode, inference, type safety |
| Tests | 25 | Comportement, couverture, testing library |
| Performance et Bundle | 25 | Re-renders, memoisation, code splitting, bundle size |
1. Hooks et Composition (30 points)
Arbre de decision : Analyse d'un composant
Le composant utilise-t-il des hooks ?
OUI --> Les hooks sont-ils appeles au top level ?
NON --> CRITIQUE : violation Rules of Hooks
OUI --> Les dependances de useEffect sont-elles completes ?
NON --> MAJEUR : stale closures possibles
OUI --> useEffect declenche-t-il des re-renders en boucle ?
OUI --> CRITIQUE : boucle infinie potentielle
NON --> OK
Le composant depasse-t-il 200 lignes ?
OUI --> Peut-il etre decompose en composants plus petits ?
OUI --> MINEUR : proposer extraction
NON --> Justification documentee ?
NON --> MAJEUR : composant monolithique
useEffectEvent — Dépendances de useEffect (React 19.2+)
useEffectEvent est stable depuis React 19.2. Recommander son usage quand des dépendances sont ajoutées à useEffect uniquement pour lire une valeur à jour (pattern "latest ref without re-sync").
// MAUVAIS : theme dans les deps → reconnexion inutile
useEffect(() => {
const conn = createConnection(roomId);
conn.on('connected', () => showNotification(theme));
conn.connect();
return () => conn.disconnect();
}, [roomId, theme]); // theme force un re-run
// BON : useEffectEvent extrait la logique event
const onConnected = useEffectEvent(() => {
showNotification(theme); // lit toujours la valeur courante
});
useEffect(() => {
const conn = createConnection(roomId);
conn.on('connected', () => onConnected());
conn.connect();
return () => conn.disconnect();
}, [roomId]); // ✅ theme n'est plus une dépendance
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.
- 7d ago Changed · +4 lines d7fc337d17c8
- 1mo ago First seen · 529 lines · 24 tokens per session scan A 71adea4fedc8
react-reviewer is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 4,402 once invoked, about $0.0001 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-30.
Other agents, from other repositories
react-expert
React patterns, hooks, state management, and performance optimization. Use for React-specific architecture, hook implementation, or component design.
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, verification, and documentation. Use for comprehensive PR reviews or code quality audits.
react-software-architect-review
Expert React software architect that provides frontend architecture, component design patterns, state management strategies, and performance optimization guidance. Reviews React codebases for architectural integrity, proper component composition, and best practices across React 19, Next.js, Remix, and modern frontend…
phase-verifier
Fresh-context acceptance verifier dispatched by /implementation:implement-dispatch at phase boundaries and for post-phase source commits: checks a phase's binary acceptance criteria against the actual diff with the orchestrator's rationale withheld, and returns a per-criterion verdict grounded in direct evidence. Its…
compare-labeler
Read-only labeler for /docs-hygiene:compress compare: labels every difference between two versions of a skill directory and returns rows plus a VERDICT line. Dispatched by /docs-hygiene:compress; not intended for direct ad-hoc use.
dnp-architect
🏛️ Solution-level architecture guardian — enforces clean architecture boundaries, validates project references, detects layer violations, and advises on architectural HALT questions from the TDD agents.