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 skills/techymt/claude-code-superpowers/naming-conventionsnpx skills add TechyMT/claude-code-superpowers --skill naming-conventionsgit clone --depth 1 https://github.com/TechyMT/claude-code-superpowersWrote 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/techymt/claude-code-superpowers/naming-conventions)<a href="https://agentmods.dev/skills/techymt/claude-code-superpowers/naming-conventions"><img src="https://agentmods.dev/badge/skills/techymt/claude-code-superpowers/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.00100 | $0.01637 |
| Opus 5 | $0.00050 | $0.00818 |
| Sonnet 5 | $0.00020 | $0.00327 |
| Haiku 4.5 | $0.00010 | $0.00164 |
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 4d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Conventions
The pattern
Claude Code uses a set of naming conventions that encode the role of a file or identifier in its name. A file named BashTool.tsx is a Tool implementation with UI concerns. A file named BashTool.ts is a Tool implementation with no UI. A function named isConcurrencySafe returns a boolean about concurrency. A function named getBranch fetches a value. A constant named MAX_STATUS_CHARS is a numeric limit. These are not accidental — reading the name tells you the role without reading the implementation.
Why this matters
At ~512K lines across 1,884 files, Claude Code is too large for any individual to hold in memory. Naming conventions serve as a file-system-level type system: you can predict what's in a file before opening it. AgentTool/AgentTool.tsx will export a Tool<Input, Output> that has UI progress output. state/AppStateStore.ts will export the AppState type and initial state. hooks/useCanUseTool.ts will export a React hook returning a permission-checking function.
How to apply it
Files:
- Tools:
src/tools/[Name]Tool/[Name]Tool.ts[x]—.tsxif the tool renders JSX output - Commands:
src/commands/[kebab-name]/index.tsorsrc/commands/[kebab-name].ts - React hooks:
src/hooks/use[Name].ts— always prefixed withuse - React components:
src/components/[Name].tsx - Utilities:
src/utils/[name].ts— lowercase, describe the domain (e.g.,git.ts,path.ts) - Types:
src/types/[name].ts— lowercase file, PascalCase exports
Identifiers:
- Types, interfaces, classes:
PascalCase(e.g.,ToolUseContext,AppState,PermissionResult) - Functions:
camelCasestarting with a verb (e.g.,createTaskStateBase,normalizeMessages,getGitStatus) - Booleans and boolean-returning functions:
is/hasprefix (e.g.,isConcurrencySafe,isReadOnly,hasWorktreeChanges,isENOENT) - Event handlers and callbacks:
on[Event]prefix (e.g.,onProgress,onChangeAppState,onCompactProgress) - Constants:
UPPER_SNAKE_CASEfor numeric/string limits;PascalCasefor object constants (e.g.,MAX_STATUS_CHARS,IDLE_SPECULATION_STATE) - Tool exports: named constant matching the file name (e.g.,
export const BashTool,export const FileReadTool) - Async functions: same naming as sync — the
Promisereturn type is the indicator, not a naming convention
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.
- 4d ago First seen · 132 lines · 100 tokens per session scan A 01dc982e5d71
naming-conventions is a skill published in the GitHub repository TechyMT/claude-code-superpowers (5 stars, last pushed 5mo ago), licensed MIT. It adds 100 tokens to every session and 1,637 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…