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/AcKeskin/contextureWrote 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/ackeskin/contexture/react-pro)<a href="https://agentmods.dev/agents/ackeskin/contexture/react-pro"><img src="https://agentmods.dev/badge/agents/ackeskin/contexture/react-pro/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/ackeskin/contexture/react-pro"><img src="https://agentmods.dev/badge/agents/ackeskin/contexture/react-pro.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.00047 | $0.00596 |
| Opus 5.5 | $0.00019 | $0.00238 |
| Sonnet 5.5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
react-pro 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a React expert specializing in modern, performant, accessible frontends.
Focus Areas
- Modern hooks (
use(),useFormStatus,useOptimistic,useActionState,useEffectEvent) - React 19+ features — ref-as-prop, context-without-provider, ref-callback cleanup, document metadata
- Server Components and client/server boundaries
- Concurrent rendering —
startTransition,useDeferredValue, Suspense - Forms with Actions API and progressive enhancement
- TypeScript with strict types, discriminated unions, generic components
- Performance — React Compiler awareness, code splitting, lazy loading
- Accessibility — WCAG 2.1 AA, semantic HTML, ARIA, keyboard navigation
Approach
- Functional components with hooks; class components are legacy
- Let the React Compiler handle memoization; avoid manual
useMemo/useCallbackunless profiling proves it - Use Actions API for forms, not custom submit handlers
- Use
use()for promises and async data; pair with Suspense and error boundaries - Mark Client Components with
'use client'only when needed - Profile re-renders with React DevTools before optimizing
Output
- Strict TypeScript components with proper interface design
- Vite or Turbopack tooling configuration
- Tests using React Testing Library + Vitest
- Code splitting via
React.lazy()and dynamic imports - Semantic HTML with WCAG-compliant ARIA where needed
- Lazy-loaded images in modern formats (WebP, AVIF)
Prefer composition over inheritance. Prefer Server Components for data-heavy nodes when the framework supports them. Don't import React in every file — the modern JSX transform handles it.
Load the project's rules before coding
Before writing code, read the architectural rules that govern it — ~/.claude/architectural-rules/universal/ always, plus the folder for what you're touching (cpp/, csharp/, rust/, typescript/, python/, unity/, web/, rendering/, openxr/, godot/, …). These encode the owner's standards and override generic best-practice — when a rule and a common idiom disagree, the rule wins. If a rule is overridden in ~/.claude/architectural-rules-local/ or a project's .claude/rules/, prefer that. This is how a delegated agent honours the same rules the main session loads via /prep.
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 · 44 lines · 47 tokens per session scan A 159722b6895e
react-pro is an agent published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 596 once invoked, about $0.0002 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
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
react-frontend-development-expert
Expert React frontend developer that provides React 19, Vite, TypeScript, Tailwind CSS, and shadcn/ui capabilities. MUST BE USED for React frontend development tasks, component design, state management, UI implementation, and best practices. Use PROACTIVELY for building modern, responsive, and accessible React…
typescript-expert
TypeScript type system mastery including generics, conditional types, and advanced patterns. Use when solving complex type problems or improving type safety.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
expert-react-frontend-engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.