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/melodic-software/claude-code-plugins/name-it-betternpx skills add melodic-software/claude-code-plugins --skill name-it-bettergit clone --depth 1 https://github.com/melodic-software/claude-code-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/melodic-software/claude-code-plugins/name-it-better)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/name-it-better"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/name-it-better.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.1 | $0.00150 | $0.03270 |
| Opus 5 | $0.00075 | $0.01635 |
| Sonnet 5 | $0.00030 | $0.00654 |
| Haiku 4.5 | $0.00015 | $0.00327 |
Grade A, and why
name-it-better 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 today.
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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name it better
Purpose
Produce better name candidates for anything that needs one: an identifier, file, module, skill, repo, or domain term. Then hand the human a scored shortlist to choose from. The dominant trigger is a reactive retry: a name was just suggested and rejected, and the same context that produced it will only produce more of the same. So the generators run BLIND to the conversation, from distinct lenses, to break the anchor. A blank-slate naming request is the same machinery without a rejected incumbent.
The human always picks. This skill narrows and recommends; it never auto-locks a name.
Criteria. Cite the source of truth, do not copy it
Score against the consuming organization's naming criteria, resolved from its own context, never from a baked-in path:
- Declared conventions win. When the consuming project names where its
naming and domain-language conventions live, its
CLAUDE.md,.claude/rules/, or a shared standards source it points to, score against THAT. Read the criteria there; do not restate them here. A criterion the user wants that is missing from those conventions flows UP into them (their standards change), not hardcoded into this skill. - None declared → the general criteria grounded in
context/sources.md, applied in this research-ordered priority. A higher tier breaks ties over every tier below it:- Semantic accuracy (anti-misleading). The name must not lie about what the thing does. A misleading name is empirically worse than a vague or meaningless one, so this outranks everything below.
- Scope fit. Length and detail scale with the thing's scope and lifetime; never repeat information the surrounding context (package, type, module) already supplies.
- Comprehensibility. Prefer full, intention-revealing words over
abbreviations, bounded: established idioms and conventionally short
names (loop
i, a receiver) are not penalised. - Trigger / evocative utility. How well the name cues recall at the moment of use. That is a genuine tiebreaker, but the lowest-priority one.
What ships with it
2 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.
- today Changed · -1 lines · -3 tokens per session 36e57850ae7a
- 2d ago First seen · 261 lines · 153 tokens per session scan A 77543dbf44ca
name-it-better is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 3,270 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
linkedin-engine
Daily interactive LinkedIn session: feed posts, DM outreach, prospect research, engagement tracking, and performance review. Human-in-the-loop. Designed for daily /loop.
reddit-reply
Daily follow-up on Reddit engagement. Reads recent reddit-monitor reports, checks each URL for replies to our comments, and drafts follow-up responses. Designed for daily /loop. Load identity and brand-voice first.
social-media-guide
Entry point for social-media — routes to LinkedIn, Reddit, X/Twitter, and the daily social brief.
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
find-shortest-path
For pathfinding and search: shortest path, maze solving, game AI, route planning, graph traversal, BFS/DFS, Dijkstra, A problems.