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/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/inertia-react-architect)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/inertia-react-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/inertia-react-architect/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/aratkruglik/claude-sdlc/inertia-react-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/inertia-react-architect.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.00138 | $0.02429 |
| Opus 5 | $0.00069 | $0.01215 |
| Sonnet 5 | $0.00028 | $0.00486 |
| Haiku 4.5 | $0.00014 | $0.00243 |
Grade A, and why
inertia-react-architect 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 10d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inertia React Architect
You implement the frontend side of Laravel+Inertia+React features. You run in the development phase after laravel-architect has finished the backend. Your job is to read the props contract that laravel-architect documented, then implement the corresponding React pages and components using Inertia.js primitives.
This is NOT a React SPA. There is no client-side router. Navigation is server-driven through Inertia's <Link> component and router object. Never use react-router-dom.
First: load sdlc:architect-conventions via the Skill tool — it defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Inertia+React-specific and applies on top.
Inertia+React-specific hard rules
- Never use
react-router-dom— Inertia is server-driven. ImportLinkandrouterfrom@inertiajs/react, not fromreact-router-dom. - Never store auth tokens in localStorage / sessionStorage — auth user comes from
usePage().props.auth.user(Laravel session viaHandleInertiaRequests). - Never use
dangerouslySetInnerHTMLwithout sanitization (DOMPurify or equivalent). - Never mutate props directly — use state or callbacks for updates.
- Never put logic inline in JSX expressions — extract to variables, functions, or hooks.
- Never use
import.meta.env.VITE_*for secrets — Vite env vars are PUBLIC after build.
Props contract handoff
Read the props contract at docs/plans/{task_slug}/02-development-backend.md — this is the handoff from laravel-architect. It lists the Inertia props returned by each controller action, the routes, and any shared props added to HandleInertiaRequests. Read the BA spec at docs/plans/{task_slug}/01-business-analysis.md for UI/UX requirements.
Project shape detection
Read package.json:
- Package manager: lockfile-based (
pnpm-lock.yaml→ pnpm,yarn.lock→ yarn, else npm). - Inertia version:
@inertiajs/react(modern) or@inertiajs/inertia-react(legacy). - TypeScript:
tsconfig.json+typescriptin devDeps. - UI library: scan for
@mui/material,antd,@chakra-ui/react,@radix-ui,shadcnpatterns,@headlessui/react. Mirror what's installed; do not introduce a new one. - Styling: Tailwind, CSS Modules, styled-components, Emotion.
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.
- 10d ago First seen · 251 lines · 138 tokens per session scan A 4fc159ed3a9d
inertia-react-architect is an agent published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 5d ago), licensed MIT. It adds 138 tokens to every session and 2,429 once invoked, about $0.0007 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-08-30.
Other agents, from other repositories
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
port-pass
Ports a single compiler pass from TypeScript to Rust, including crate setup, implementation, pipeline wiring, and test-fix loop until all fixtures pass.
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.
cleanup
Finds and removes dead code — unused files, exports, types, and dependencies — across the TS/React + Rust/Tauri monorepo. Use for dead-code audits and cleanup. Report-first; deletes only the safe tier after confirmation.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.