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/audit-architecturenpx skills add aleolidev/claude-react-kit --skill audit-architecturegit 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/audit-architecture)<a href="https://agentmods.dev/skills/aleolidev/claude-react-kit/audit-architecture"><img src="https://agentmods.dev/badge/skills/aleolidev/claude-react-kit/audit-architecture.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.00490 |
| Opus 5 | $0.00007 | $0.00245 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
audit-architecture 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
Architecture Audit
Perform a comprehensive audit of the codebase architecture. Check for:
1. Cross-Feature Imports
Search for any feature importing from another feature:
grep -rn "from.*@/features/" src/features/ --include="*.ts" --include="*.tsx" | while read line; do
FILE=$(echo "$line" | cut -d: -f1)
FEATURE=$(echo "$FILE" | sed -n 's|.*/features/\([^/]*\)/.*|\1|p')
IMPORT=$(echo "$line" | grep -o "@/features/[^/]*" | sed 's|@/features/||')
if [ "$FEATURE" != "$IMPORT" ]; then
echo "VIOLATION: $line"
fi
done
2. Core Domain Leakage
Check if core/ imports from features/ or shared/:
grep -rn "from.*@/features/\|from.*@/shared/" src/core/ --include="*.ts" --include="*.tsx"
3. Design System Purity
Check if design-system/ has business logic imports:
grep -rn "from.*@/features/\|from.*@/shared/" src/design-system/ --include="*.ts" --include="*.tsx"
4. Oversized Files
Find files exceeding 200 lines:
find src/ -name "*.tsx" -o -name "*.ts" | xargs wc -l | sort -rn | head -20
5. Empty Directories
find src/ -type d -empty
6. Duplicate Naming
Search for potential duplicate folders/files with different casings.
7. Components Fetching Data
Search for useQuery/useMutation inside component directories (not pages):
grep -rn "useQuery\|useMutation" src/features/*/components/ src/shared/components/ src/design-system/ --include="*.tsx"
Report all violations found with specific file paths and recommended fixes.
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 · 65 lines · 14 tokens per session scan A e641bf905ad8
audit-architecture 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 490 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.