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.
npx agentmods add skills/aleolidev/claude-react-kit/setupnpx skills add aleolidev/claude-react-kit --skill setupgit clone --depth 1 https://github.com/aleolidev/claude-react-kitWhat 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 | $0.00022 | $0.01654 |
| Opus 5 | $0.00011 | $0.00827 |
| Sonnet 5 | $0.00004 | $0.00331 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-react-kit — Setup
You are setting up claude-react-kit in this project. Your job is to analyze the codebase, understand its real stack and conventions, and generate perfectly customized configuration files.
Phase 1: Deep Analysis
Analyze the project thoroughly. Read and extract information from:
package.json— framework, dependencies, scripts, package manager (check forpackageManagerfield too)- Lock file — which exists? (
package-lock.json,yarn.lock,pnpm-lock.yaml,bun.lock,bun.lockb) tsconfig.json— path aliases, strict mode, baseUrl, target- Framework config —
next.config.*,vite.config.*,app.json/app.config.*(Expo),metro.config.*,remix.config.* - Linter/formatter —
.eslintrc*,eslint.config.*,.prettierrc*,biome.json - Existing
CLAUDE.md— if one exists, read it to preserve any project-specific rules the user already has - Existing
.claude/— if it exists, read settings.json and any custom rules to preserve them - Source directory structure —
ls src/or equivalent to understand the current architecture (do they already have features/, shared/, core/, design-system/, or different names?) - Routing —
ls app/orls pages/orls src/screens/to understand routing structure - State management patterns — grep for store/slice/atom definitions to understand actual usage
- Test setup —
jest.config.*,vitest.config.*, test file patterns - CI/CD —
.github/workflows/, check what checks run
Build a complete mental model of the project before writing anything.
Phase 2: Ask What You Can't Detect
After analysis, present your findings to the user in a concise summary:
Here's what I detected:
- Framework: [X]
- Package manager: [X]
- Source structure: [describe what you found]
- State management: [X]
- Testing: [X]
- Styling: [X]
- Existing CLAUDE.md: [yes/no, summary if yes]
- Path aliases: [X]
Then ask ONLY about things you genuinely couldn't determine:
- If the architecture doesn't clearly match the 5-layer model, ask how they want to map their directories
- If there are conventions you noticed but aren't sure if they're intentional
- If there's an existing CLAUDE.md, ask what to keep vs replace
- Any ambiguities in their setup
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 · 150 lines · 22 tokens per session scan A ebe9f386cb3a
setup is a skill published in the GitHub repository aleolidev/claude-react-kit (2 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 1,654 once invoked, about $0.0001 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-31.
Other skills, from other repositories
design-patterns
Rust design patterns for RTK. Newtype, Builder, RAII, Trait Objects, State Machine. Applied to CLI filter modules. Use when designing new modules or refactoring existing ones.
codebase-onboarding
Use when you land in an unfamiliar or inherited codebase and must get productive fast: a breadth-first map of entry points, request flow, module ownership, hidden side effects (cron, webhooks, workers) and churn hotspots, committed as CODEBASE-MAP.md. NOT a deep audit of one module (that is analyze) or chasing one…
frontend-feature
Build a frontend feature end-to-end. Routing, data, state, forms, types, all UI states, tests. Reuse first.
database-migrations
Write safe, reversible, backward-compatible database migrations. Avoid downtime, locks, and "oops we lost data".
postgres-supabase
Postgres + Supabase specifics — RLS, migration workflow, schema cache, auth integration, common pitfalls.
refactor-planner
Plan a safe step-by-step refactor. Expand-then-contract; every step ships green; rollback per step.