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 tslateman/duet --skill naminggit clone --depth 1 https://github.com/tslateman/duetWrote 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/tslateman/duet/naming)<a href="https://agentmods.dev/skills/tslateman/duet/naming"><img src="https://agentmods.dev/badge/skills/tslateman/duet/naming/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/tslateman/duet/naming"><img src="https://agentmods.dev/badge/skills/tslateman/duet/naming.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.00055 | $0.01620 |
| Opus 5.5 | $0.00022 | $0.00648 |
| Sonnet 5.5 | $0.00011 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
naming 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming as Design
Overview
Naming difficulty is a design smell. When you struggle to name something, the abstraction is wrong. Use naming as a lens to surface confused boundaries, mixed responsibilities, and domain misunderstanding.
Benner's Four Principles
Every name balances four properties. When they conflict, make the tradeoff deliberate.
- Understandability, Describe the context it represents. A reader should know what it does without reading the implementation
- Conciseness, Use only the words necessary. Longer is not clearer if the extra words add no meaning
- Consistency, Same word means the same thing everywhere. Different things get different names
- Distinguishability, A name must be distinct from its neighbors. Similar names for different things cause bugs
See references/principles.md for detailed rules and naming smells.
Two Modes
Review Mode
Examine names in recently changed code:
- Read the changed code
- For each name, ask:
- Does it pass all four principles?
- Could a reader understand this without context?
- Is the verb specific? ("process", "handle", "manage" almost never are)
- Does it match the domain language?
- Surface violations with specific alternatives
Design Mode
When naming is hard, use the struggle as a diagnostic:
- What does this thing actually do? List its responsibilities
- If the list has more than one item, the naming problem is a design problem, split it
- Who calls it? What do they expect?
- If it disappeared, what would break? That's what it is
- What would the domain expert call it?
Naming Smells
Names that signal design confusion:
| Smell | Example | What it reveals |
|---|---|---|
| Generic verb | handleData, processRequest |
Unclear responsibility |
Suffix -Manager, -Helper, -Utils |
UserManager, StringHelper |
God object or junk drawer |
| And/Or in name | validateAndSave |
Two responsibilities |
| Type in name | userList, nameString |
Redundant or wrong abstraction level |
| Negated boolean | isNotReady, disableFeature |
Double negatives in conditions |
| Abbreviated beyond recognition | usrSvcRsp |
Conciseness without understandability |
What ships with it
1 file 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.
- 1mo ago First seen · 166 lines · 55 tokens per session scan A bf4b229d0eb7
naming is a skill published in the GitHub repository tslateman/duet (1 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,620 once invoked, about $0.0002 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
git-workflow
Manages branches, worktrees, atomic commits, and branch completion by merge, PR, preserve, or discard. Use when starting feature work that needs a branch or an isolated workspace, making commits during development, or finishing a development branch. Also use when the user says "set up worktree", "create PR", "finish…
release
Automates the full release workflow: version bump, git tag, GitHub release, and npm publish.
find
Find the local coding-agent session that wrote the uncommitted changes in a file, or in a pasted snippet of changed code or comment text, and give a one-line command that resumes it. Prefers the session that authored the change over a review session. Use when asked which session, chat, thread, or agent made an edit…
git-workflow
Perform requested Git actions while preserving user work. Triggers on "commit", "提交".
quick-wrap
Short session close: commit, loose ends, stop. Not workstream-complete.
run
The single lifecycle entry point — take one or more tickets and drive each through its whole lifecycle (investigate, red tests, implement, gates, review, PR, merge, archive), interleaving them. Lean by default — one worker per ticket runs red tests, implementation and the gate scripts in one worktree, then…