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 agents/dannykkh/skill-olympus/naming-conventionsgit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/agents/dannykkh/skill-olympus/naming-conventions)<a href="https://agentmods.dev/agents/dannykkh/skill-olympus/naming-conventions"><img src="https://agentmods.dev/badge/agents/dannykkh/skill-olympus/naming-conventions.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.00031 | $0.00830 |
| Opus 5 | $0.00015 | $0.00415 |
| Sonnet 5 | $0.00006 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
naming-conventions 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 5d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Conventions (Optional Reference)
명시적으로 불러 쓰는 네이밍 참고 규칙. 상세 분석은 naming-analyzer 스킬 사용.
Language Conventions
| 언어 | 변수/함수 | 클래스 | 상수 | Boolean |
|---|---|---|---|---|
| JavaScript/TS | camelCase | PascalCase | UPPER_SNAKE | is/has/can |
| Python | snake_case | PascalCase | UPPER_SNAKE | is_/has_/can_ |
| Java | camelCase | PascalCase | UPPER_SNAKE | is/has/can |
| Go | camelCase (내부), PascalCase (외부) | PascalCase | UPPER_SNAKE | - |
Boolean Prefixes
| Prefix | 용도 | 예시 |
|---|---|---|
| is | 상태 | isActive, isVisible, isLoggedIn |
| has | 소유 | hasPermission, hasError, hasChildren |
| can | 능력 | canEdit, canDelete, canSubmit |
| should | 결정 | shouldRender, shouldValidate |
Common Issues
❌ 모호한 이름
// Bad
function process(data) { }
const info = getData();
let temp = x;
// Good
function processPayment(transaction) { }
const userProfile = getUserProfile();
let previousValue = x;
❌ 오해를 일으키는 이름
// Bad - 이름과 동작 불일치 (side effect 있음)
function getUser(id) {
user.lastLogin = Date.now(); // 변경!
saveUser(user); // 저장!
return user;
}
// Good
function fetchAndUpdateUserLogin(id) { ... }
❌ 약어 남용
// Bad
const usrCfg = loadConfig();
function calcTtl(arr) { }
// Good
const userConfig = loadConfig();
function calculateTotal(amounts) { }
// OK - 널리 알려진 약어
const htmlElement, apiUrl, userId;
❌ 매직 넘버
// Bad
if (age > 18) { }
setTimeout(cb, 3600000);
// Good
const LEGAL_AGE = 18;
const ONE_HOUR_MS = 60 * 60 * 1000;
Decision Tree
Boolean? → is/has/can/should prefix
↓ No
Function? → verb phrase (action)
↓ No
Class? → PascalCase noun
↓ No
Constant? → UPPER_SNAKE_CASE
↓ No
Variable → descriptive noun (camelCase/snake_case)
Function Verbs
| 동사 | 용도 |
|---|---|
| get/fetch | 조회 |
| create/add | 생성 |
| update/set | 수정 |
| delete/remove | 삭제 |
| validate/check | 검증 |
| parse/format | 변환 |
| calculate/compute | 계산 |
Best Practices
✅ DO:
- 전체 단어 사용 (약어 최소화)
- 구체적이고 명확하게
- 언어 컨벤션 준수
- Boolean은 명확하게
- 상수에 단위 포함 (TIMEOUT_MS)
❌ DON'T:
- 단일 문자 (루프 제외: i, j, k)
- 모호한 이름 (data, info, temp)
- 컨벤션 혼용
- 오해의 소지 있는 이름
- 과도한 약어
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.
- 5d ago First seen · 128 lines · 31 tokens per session scan A c32fa707e284
naming-conventions is an agent published in the GitHub repository Dannykkh/skill-olympus (5 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 830 once invoked, about $0.0002 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 agents, from other repositories
document-steward
GOAL: One document per domain. Minimum tokens for maximum clarity.
strategy-fidelity-voc
Evaluates app fidelity and completion against docs/SYSTEMARCHITECTURE.md and domain references. Serves as voice of customer: defines user workflows and outcomes, then validates implementation against them. Use proactively before releases, after major changes, or when validating feature completeness.
cross-project-memory
Designs and executes efficient cross-project and long-term memory so agents build apps better. Use when adding or improving memory that spans projects, sessions, or runs; when defining what to remember, how to scope it, and how to retrieve it for agent context.
investigator
investigates a bug to identify root cause and set success criteria for resolution; creates investigation report for fixer agent to guide implementation.
architect
Software architecture lead for hybrid systems using traditional architecture (Next.js + PostgreSQL) and AI-agent-supportive architecture (ruvector). Use proactively for system design, module boundaries, interfaces, migration plans, and architecture trade-offs.
ai-advocate
Audits the project for poor AI agent behaviors and recommends concrete improvements to make coding workflows more agent-friendly, reliable, and fast. Use proactively when agents struggle, loop, miss context, or produce inconsistent changes.