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 codebygarv/Ai-skills --skill naming-consultantgit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/naming-consultant)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/naming-consultant"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/naming-consultant/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/codebygarv/ai-skills/naming-consultant"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/naming-consultant.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.00042 | $0.00533 |
| Opus 5 | $0.00021 | $0.00267 |
| Sonnet 5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
naming-consultant 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Suggest clear, consistent names for code elements (variables, functions, classes, files) based on what they actually do and the naming conventions already in use nearby — not generic naming advice detached from context.
When to Use
- A name feels vague, misleading, or inconsistent with the rest of the codebase.
- Naming something new and want options grounded in existing conventions.
- Reviewing a PR and a name doesn't clearly communicate intent.
What to Analyze / Do
- Understand what the thing actually does — a name should reflect behavior/purpose, not implementation detail that might change.
- Check surrounding naming conventions — casing style (camelCase/snake_case/PascalCase), verb conventions (
get/fetch/loadfor retrieval — pick whichever the codebase already uses consistently), boolean naming (is/has/shouldprefixes), and match them rather than introducing a new convention. - Avoid both extremes — names that are too generic (
data,handler,temp,item2) and names that are needlessly verbose (theListOfActiveUserAccountObjectsForCurrentSession). - Flag names that actively mislead — a variable named
userListthat's actually aMap, or a function namedgetUserthat also has a side effect (writes to the database) — naming should reflect what the code actually does, and misleading names are a correctness/trust issue, not just style. - Offer 2-3 alternatives when there's genuine ambiguity about the best name, with a brief note on the trade-off between them.
Output Format
- For each name reviewed: current name → issue (if any) → suggested name(s) → why.
- Group by whether the issue is "unclear/generic" vs. "actively misleading" — misleading names are higher priority to fix.
- If suggesting a new name for something not yet named, give 2-3 options with the reasoning for each.
Avoid
- Suggesting a rename purely for personal stylistic preference when the current name is clear and follows existing conventions.
- Recommending a naming convention that conflicts with what the rest of the codebase already consistently uses.
- Over-explaining trivial, already-clear names — focus effort on the ones that are actually unclear or misleading.
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.
- 5d ago First seen · 35 lines · 42 tokens per session scan A 9301df25519f
naming-consultant is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 533 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-09-03.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…