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 msbaek/msbaek-claude-plugins --skill naming-processgit clone --depth 1 https://github.com/msbaek/msbaek-claude-pluginsWrote 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/msbaek/msbaek-claude-plugins/naming-process)<a href="https://agentmods.dev/skills/msbaek/msbaek-claude-plugins/naming-process"><img src="https://agentmods.dev/badge/skills/msbaek/msbaek-claude-plugins/naming-process/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/msbaek/msbaek-claude-plugins/naming-process"><img src="https://agentmods.dev/badge/skills/msbaek/msbaek-claude-plugins/naming-process.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.00118 | $0.03497 |
| Opus 5.5 | $0.00047 | $0.01399 |
| Sonnet 5.5 | $0.00024 | $0.00699 |
| Haiku 4.5 | $0.00012 | $0.00350 |
Grade A, and why
naming-process 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 1mo 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming as a Process
GOAL
Arlo Belshee의 6단계 네이밍 진화와 Clean Code 7가지 네이밍 원칙을 적용하여:
- 코드의 의도(what이 아니라 why)를 이름으로 명확히 전달 — "이름을 신뢰하면 메서드 본문을 읽을 필요가 없는" 상태가 목표
- Naming Smells 제거
- 도메인 언어를 코드로 표현
CONSTRAINTS
- 계열: Tidy — 후보 보고 후 승인 없이 적용 (
../../references/refactoring-procedure.md§0·§3-A) - 동작 변경 금지: 구조 개선만 수행 (기능 변경 없음)
- 테스트 수정 금지: 구조 변경이 테스트를 실패시키면 되돌리기
- 명시적 git add:
git add -A금지, 변경된 파일만 명시
6단계 네이밍 프로세스
- Obvious Nonsense → 2. Honest → 3. Completely Honest → 4. Does the Right Thing → 5. Intent Revealing → 6. Domain Abstraction
예시: 네이밍 진화
// 1. Obvious Nonsense
int x;
// 2. Honest (타입 반복)
int intValue;
// 3. Completely Honest (맥락 포함)
int orderItemCount;
// 4. Does the Right Thing (역할 명확)
int itemsInCart;
// 5. Intent Revealing (의도 표현)
int pendingOrderItems;
// 6. Domain Abstraction (도메인 언어)
int itemsAwaitingFulfillment;
Clean Code 7가지 네이밍 원칙
| # | 원칙 | 핵심 | 예시 |
|---|---|---|---|
| 1 | Reveal Your Intent | 동작이 아니라 목적을 담는다 | process() → placeOrder() |
| 2 | Describe the Problem | 매직 값 대신 도메인 언어 | INCLUDE_FIRST → OPEN_LEFT, TWENTYFOURBITGROUP → BITS_PER_GROUP |
| 3 | Avoid Disinformation | 타입/역할을 속이지 않는다 | accountList(실제 List 아님) → accounts |
| 4 | Pronounceable Names | 팀 대화에서 발음 가능해야 함 | genymdhms → generationTimestamp |
| 5 | Avoid Encodings | 헝가리안·타입/스코프 접두사 금지 | IService → Service, m_memberName → memberName |
| 6 | Parts of Speech | 클래스=명사, 메서드=동사, boolean=서술어 | 아래 상세 |
| 7 | The Scope Rule | scope에 따라 길이 조절 | 아래 상세 |
The Scope Rule
- 변수: scope ↑ → 이름 ↑ (정비례) — scope가 길수록 선언부-사용부 거리가 멀어져 문맥 상실 위험이 커진다. 20줄 떨어진 곳의
d는 의미가 불명확하다. - 함수/클래스: scope ↑ → 이름 ↓ (반비례) — public API는 자주 호출되므로 짧아야 하고, private 메서드는 호출처가 적어 긴 이름이 주석 역할을 대신한다.
- Public=일반적(general), Private=구체적(detailed): public 인터페이스는 상위 추상화 계약이므로 짧고 일반적으로, private 구현은 하위 디테일이므로 길고 정확하게 서술한다.
// Good: 변수 scope 규칙 (정비례)
for (int i = 0; i < 10; i++) { ... } // 극히 짧은 scope → 짧은 이름
private Customer currentlyAuthenticatedCustomer; // 클래스 필드 → 긴 이름
static final int WORK_DAYS_PER_WEEK = 5; // 정적 필드 → 가장 긴 이름
// Good: 함수 scope 규칙 (반비례)
public void serve(Socket s) { ... } // public, 자주 호출 → 짧게
private void closeEnclosingServiceInSeparateThread() { ... } // private → 길게(자체 문서화)
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.
- 1mo ago Changed · -1 lines 62aa07027902
- 1mo ago Changed · -1 lines 1edb52dd3144
- 1mo ago First seen · 329 lines · 118 tokens per session scan A 29051965f0e3
naming-process is a skill published in the GitHub repository msbaek/msbaek-claude-plugins (8 stars, last pushed 5d ago), licensed MIT. It adds 118 tokens to every session and 3,497 once invoked, about $0.0005 per session on Opus 5.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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…