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 refactoringgit 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/refactoring)<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/refactoring"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/refactoring/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/refactoring"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/refactoring.svg" alt="Reviewed on agentmods" width="80" 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.00097 | $0.01577 |
| Opus 5 | $0.00048 | $0.00788 |
| Sonnet 5 | $0.00019 | $0.00315 |
| Haiku 4.5 | $0.00010 | $0.00158 |
Grade A, and why
refactoring 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md Refactoring Skill
CLAUDE.md 파일 분석, 구조화, 최적화를 통해 Claude Code의 프로젝트 이해도와 작업 효율성을 극대화합니다.
Workflow Decision Tree
사용자 요청 분석
├─ 새 CLAUDE.md 작성
│ └─ 템플릿 기반 생성 → references/template.md 참조
├─ 기존 CLAUDE.md 리팩토링
│ ├─ 1단계: 현재 파일 분석
│ ├─ 2단계: 문제점 식별
│ ├─ 3단계: 구조 재설계
│ └─ 4단계: 컨텍스트 최적화
└─ CLAUDE.md 검토/평가
└─ 품질 메트릭 기반 분석
Step 1: 분석 (Analysis)
현재 CLAUDE.md 평가 체크리스트
□ 필수 섹션 포함 여부
- [ ] Header (프로젝트명 + 설명)
- [ ] Technical Stack & Conventions
- [ ] Path Aliases
- [ ] Critical Development Rules
- [ ] NOT TO DOs
□ 컨텍스트 효율성
- [ ] 토큰 예산 효율적 사용
- [ ] 중복 정보 없음
- [ ] 코드 예제 > 장황한 설명
□ 오류 방지 패턴
- [ ] ✅/❌ 패턴 사용
- [ ] Common Mistakes 테이블
- [ ] 구체적 필드명/경로명
□ 아키텍처 문서화
- [ ] 레이어 구조 다이어그램
- [ ] Forbidden Patterns
- [ ] 파일/디렉토리 구조
문제점 식별 패턴
| 문제 유형 | 증상 | 해결책 |
|---|---|---|
| 정보 부족 | Claude가 스키마/타입을 자주 물어봄 | Database Schema 섹션 추가 |
| 모호한 규칙 | 같은 실수 반복 | ✅/❌ 코드 예제로 구체화 |
| 과도한 정보 | 토큰 낭비, 핵심 놓침 | 테이블/코드로 압축 |
| 구조 혼란 | 필요 정보 찾기 어려움 | 섹션 재구성, 목차 추가 |
Step 2: 구조화 (Structure)
필수 섹션 순서
- Header - 프로젝트명 + 1-2문장 설명
- Technical Stack & Conventions - 프레임워크, UI, 상태관리
- Path Aliases -
@/경로 매핑 - Database Schema Overview - 테이블 요약 + 주의사항
- Critical Development Rules - ✅/❌ 패턴
- Architecture Patterns - 레이어 다이어그램
- Workflow Notes - 작업 전 체크리스트
- NOT TO DOs - 금지 사항 목록
- Reference Documentation - 상세 문서 링크
상세 가이드
- Implementation Guide - 전체 구현 가이드
- Template - 복사 가능한 템플릿
- Design Patterns - 고급 패턴 모음
Step 3: 최적화 (Optimization)
컨텍스트 압축 기법
Before (72 tokens):
When you need to get students from the database, you should always use the service layer functions that are located in the /lib/services directory. Never import the Supabase client directly into your components.
After (28 tokens):
### Data Access - Use Service Layer
// ✅ CORRECT
import { getStudents } from '@/lib/services/students'
// ❌ WRONG
import { createClient } from '@/lib/supabase/client'
What ships with it
4 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 · 181 lines · 97 tokens per session scan A d61f7b4e52c8
refactoring is a skill published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,577 once invoked, about $0.0005 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.