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 jackchuka/skills --skill project-namergit clone --depth 1 https://github.com/jackchuka/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/jackchuka/skills/project-namer)<a href="https://agentmods.dev/skills/jackchuka/skills/project-namer"><img src="https://agentmods.dev/badge/skills/jackchuka/skills/project-namer/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/jackchuka/skills/project-namer"><img src="https://agentmods.dev/badge/skills/jackchuka/skills/project-namer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 78 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00023 | $0.00906 |
| Opus 5.5 | $0.00009 | $0.00362 |
| Sonnet 5.5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
project-namer 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Namer
Overview
Guide users from vague naming requirements to a memorable, unique name through structured exploration of scope, constraints, and style preferences.
When to Use
- Naming a new repository, project, tool, or product
- User is unsure what to call something
- User rejects initial suggestions as "too generic" or "too vendor-specific"
Core Workflow
digraph naming {
rankdir=TB;
"Understand scope" -> "Clarify constraints" -> "Offer style categories" -> "Generate options" -> "Iterate on feedback" -> "Converge";
"Iterate on feedback" -> "Offer style categories" [label="style shift"];
"Iterate on feedback" -> "Generate options" [label="refine"];
}
1. Understand Scope
Ask what the project contains and does:
- Single purpose or multi-purpose?
- What goes in it? (code, docs, tools, configs)
- Who uses it? (personal, team, public)
2. Clarify Constraints
Identify naming constraints:
- Vendor lock-in concerns? (avoid "claude-tools", "openai-kit")
- Technical limits? (npm name available, no special chars)
- Must work as CLI command? (short, typeable)
3. Offer Style Categories
Present naming styles - let user pick direction:
| Style | Examples | When to suggest |
|---|---|---|
| Functional | toolkit, dev-tools, workflows | User wants clarity over personality |
| Character/Butler | friday, jeeves, pennyworth | User wants personality, memorability |
| Compound | devbox, workstation, codekit | Balance of clear + catchy |
| Metaphor | forge, lighthouse, compass | Evokes purpose without stating it |
| Coined | vercel, kubectl, nginx | Maximum uniqueness, brand potential |
4. Generate Options
Within chosen style, generate 5-8 options. For each:
- Keep short (1-2 syllables preferred)
- Easy to pronounce (no awkward consonant clusters)
- Easy to type (avoid special chars, unusual spellings)
- Room to grow (not too narrow in scope)
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 · 117 lines · 23 tokens per session scan A b8adee080882
project-namer is a skill published in the GitHub repository jackchuka/skills (15 stars, last pushed 10d ago), licensed MIT. It adds 23 tokens to every session and 906 once invoked, about $0.0001 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-30.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).