Borrowing it
Nothing to install: this file belongs to sukirman1901/frontend-expert. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sukirman1901/frontend-expert/main/CLAUDE.mdgit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/instructions/sukirman1901/frontend-expert/claude-md)<a href="https://agentmods.dev/instructions/sukirman1901/frontend-expert/claude-md"><img src="https://agentmods.dev/badge/instructions/sukirman1901/frontend-expert/claude-md.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.1 | $0.00575 | $0.00575 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
frontend-expert CLAUDE.md 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 8d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Claude Code entry point for Frontend Expert.
Plugin assets
- Skills:
skills/(22 skills — suite rootfrontend-expert+ domain pillars; seedocs/pillars.md) - Agents:
agents/design-reviewer.md,agents/ui-developer.md,agents/test-engineer.md - Commands:
/design,/audit,/ui,/test-ui,/polish— optional - Rules:
.claude/rules/design-system.md(chat-first + judgment) - Hooks:
hooks/hooks.json(SessionStart + PostToolUse anti-slop scan) - Tokens:
tokens/*.css+ decision tree / scoring inreferences/token-preset-scoring.md(+tokens/README.md) - Evals:
evals/(E1–E23)
Default behavior (chat-first + judgment)
- Do not wait for slash commands. Map intent → skills via
AGENTS.md+ rules - Blank-canvas / ambiguous UI →
frontend-judgment(2–3 approaches) before coding - Then →
design-tokens(decision tree) → (+marketing-landingif marketing homepage) → (+ shell/data/forms) →ui-components→responsive-ui→motion(light shell; marketing = families/patterns frommotion-families.md, hand-roll) →anti-ai-slop→ui-feel→accessibility - Tests when asked →
test-engineer+frontend-testing - Audit when asked →
design-reviewerskill chain (/designor/audit); never fabricate visual scores - “Rapihin / polish sampai bagus” →
ui-quality-loop(/polish), capped iterations - Honor hook advisories from
anti-slop-scan.sh - If the project already has a design system, use custom mode (do not override with presets)
- Icons: MUST use Reicon in shipped markup unless project icon lib or text-only waiver (
references/compliance-gates.md) - Before DONE on UI builds → Conventions check including Responsive, Hierarchy, Typography, Motion, Shell, Landing (if marketing), A11y (
references/compliance-gates.md)
References
See AGENTS.md for the auto intent map, docs/pillars.md for suite pillars, docs/pack-layers.md for layers.
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.
- 8d ago First seen · 37 lines · 575 tokens per session scan A 96205e87a78c
frontend-expert CLAUDE.md is an instructions file published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed 4d ago), licensed MIT. It adds 575 tokens to every session, about $0.0029 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.