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/scaffold-featurenpx skills add aleolidev/claude-react-kit --skill scaffold-featuregit clone --depth 1 https://github.com/aleolidev/claude-react-kitWrote 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/skills/aleolidev/claude-react-kit/scaffold-feature)<a href="https://agentmods.dev/skills/aleolidev/claude-react-kit/scaffold-feature"><img src="https://agentmods.dev/badge/skills/aleolidev/claude-react-kit/scaffold-feature.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 | $0.00014 | $0.00216 |
| Opus 5 | $0.00007 | $0.00108 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
scaffold-feature 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 4d 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.
What it actually says
Scaffold Feature
Create a new feature module at src/features/$ARGUMENTS/ with the standard structure:
mkdir -p src/features/$ARGUMENTS/{components,hooks,services,types,constants,stores,locales,assets}
Create starter files:
src/features/$ARGUMENTS/locales/en.json— empty i18n object{}src/features/$ARGUMENTS/locales/es.json— empty i18n object{}src/features/$ARGUMENTS/types/index.ts— empty types filesrc/features/$ARGUMENTS/constants/index.ts— feature endpoints and query keys
Use kebab-case for the feature directory name. Confirm the feature name doesn't conflict with existing features. After creation, remind the user to register the locale files in the i18n aggregator.
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.
- 4d ago First seen · 26 lines · 14 tokens per session scan A 51c3d1d921cb
scaffold-feature is a skill published in the GitHub repository aleolidev/claude-react-kit (2 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 216 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.
code-quality-principles
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.
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…
hydra
Use when the user asks for Hydra, a deep multi-perspective code review, architecture or security tradeoffs, blind spots, or iterative re-review. Avoid for simple fixes and lookups.
universal-patterns
Use when implementing language-agnostic patterns like layered architecture, dependency injection, error handling, or code organization principles across any technology stack.
frontend-feature
Build a frontend feature end-to-end. Routing, data, state, forms, types, all UI states, tests. Reuse first.