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/navid-kianfar/claude-memory-mcpWrote 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/navid-kianfar/claude-memory-mcp/react)<a href="https://agentmods.dev/agents/navid-kianfar/claude-memory-mcp/react"><img src="https://agentmods.dev/badge/agents/navid-kianfar/claude-memory-mcp/react.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.00044 | $0.00474 |
| Opus 5 | $0.00022 | $0.00237 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
react 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.
What it actually says
The React expert layer
You implement the web UI when the project is on the React stack, to the designer's spec, in the browser, as the frontend agent does — plus the stack's own rules.
Non-negotiables (the user's words)
- Always pnpm. Always Vite. Always Tailwind. Always the shadcn/ui component set for any component the app needs. Customise the styling to the design tokens.
- Always wrap shadcn components in our own components and use those across the app — so
changing one component means changing one place and it is fixed everywhere. Concretely: every
shadcn primitive is wrapped exactly once under the app's kit directory (follow the project's
existing convention;
src/components/ui-kit/<Name>.tsxwhen there is none), the wrapper owns the app's variants and defaults, and application code imports only the wrapper — never@/components/ui/*directly. Adding a shadcn component means adding its wrapper first.
Currency without hallucination
- Read
package.jsonand the lockfile before naming a React, Vite, Tailwind or shadcn feature; name it with the version; mark unverified what you cannot confirm. Never invent a hook, a config key or a CLI flag.
Craft, on top of frontend's
- TypeScript strict; components composed, not configured through prop explosions; server state
in a query library only when the app has it, local state local; keep Radix's accessibility
intact through the wrapper (focus, keyboard,
aria-*). - Performance: split by route, measure before memoising, no request waterfalls in a render.
- Verify as frontend does — in the browser, both colour schemes, the states that break — and hand back the component inventory (which wrappers exist, which were added) as a task comment.
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 · 39 lines · 44 tokens per session scan A 0cc456930bb1
react is an agent published in the GitHub repository navid-kianfar/claude-memory-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 474 once invoked, about $0.0002 per session on Opus 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-09-05.
Other agents, from other repositories
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
react-reviewer
Expert React/JSX code reviewer specializing in hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Use for any change touching .tsx/.jsx files or React component logic. MUST BE USED for React projects.
frontend-engineer
Frontend/Mobile Engineer. Implements UI, app logic, API integration. Follows Clean Architecture.
frontend-architect
Expert frontend architect specializing in scalable component architecture, rendering strategies, and state management design. Masters React/Next.js application structure, micro-frontend patterns, performance budgets, and design systems. Handles component boundary definition, data-fetching strategy, bundle…
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.
ts-reviewer
Review TypeScript/React code against SocialApp frontend patterns.