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 skills add rungchan2/frontend-skills --skill buildergit clone --depth 1 https://github.com/rungchan2/frontend-skillsWrote 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/rungchan2/frontend-skills/builder)<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/builder"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/builder.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.00157 | $0.02610 |
| Opus 5 | $0.00078 | $0.01305 |
| Sonnet 5 | $0.00031 | $0.00522 |
| Haiku 4.5 | $0.00016 | $0.00261 |
Grade A, and why
builder 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md Builder
블록 단위로 CLAUDE.md를 생성, 검사, 정리하는 도구.
Workflow Decision Tree
사용자 요청 분석
├─ "CLAUDE.md 만들어줘" / "생성"
│ └─ Mode: BUILD → Step 1 → Step 2 → Step 3
├─ "CLAUDE.md 검사해줘" / "audit"
│ └─ Mode: AUDIT → Step 1 → Step 4
├─ "블록 추가해줘" / "이 부분 정리해줘"
│ └─ Mode: PATCH → Step 1 → Step 5
└─ "CLAUDE.md 포맷 맞춰줘" / "정리"
└─ Mode: FORMAT → Step 1 → Step 6
Step 1: Tech Stack Detection
프로젝트 분석하여 필요한 블록 결정.
Detect sources:
package.json— dependenciestsconfig.json— path aliases- Directory structure —
/app,/lib/services,/hooks,/stores,/spec - Existing
CLAUDE.md— current state
Block requirement matrix:
| Condition | Required Blocks |
|---|---|
| Always | Header, Tech Stack, NOT TO DOs |
@supabase/supabase-js detected |
Supabase, MCP & Migration, Database Tables, SSOT |
next detected |
Next.js Convention, Routing Convention |
@tanstack/react-query detected |
3-Layer Architecture, Revalidation Strategy |
zustand detected |
Auth & User State |
/spec directory exists |
Spec Files |
| Korean UI project | Terminology |
| External API integration | API Integration |
/constants or /lib/constants exists |
Constants Strategy |
Block definitions: See references/block-definitions.md for all 18 blocks.
Supabase CLI Setup (db-schema)
Supabase가 감지되면, db:schema CLI 스크립트 셋업 여부를 확인하고 없으면 설치를 제안.
Check:
package.json에"db:schema"script 있는지 확인scripts/db-schema.ts(또는 유사 파일) 존재 여부 확인
Setup (없을 때):
scripts/db-schema.ts를 프로젝트에 복사 — bundled script: scripts/db-schema.tspackage.json에 script 추가:{ "scripts": { "db:schema": "tsx scripts/db-schema.ts" } }tsxdev dependency 확인:pnpm add -D tsx(없을 때만)
Script 특성:
types/database.types.ts를 파싱하여 테이블/enum 정보를 추출- 전체 파일(4000+ lines)을 context에 로드하지 않고 필요한 부분만 조회
DB_TYPES_PATH환경변수로 경로 커스터마이징 가능 (기본:types/database.types.ts)- 대체 경로 자동 탐색:
src/types/,lib/,src/lib/ - Commands:
tables,table <name>,enums,enum <name>,search <keyword>
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 271 lines · 157 tokens per session scan A a229c15e45c3
builder is a skill published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 157 tokens to every session and 2,610 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…