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.
git clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/commands/axiomantic/spellbook/polish-repo-naming)<a href="https://agentmods.dev/commands/axiomantic/spellbook/polish-repo-naming"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/polish-repo-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/commands/axiomantic/spellbook/polish-repo-naming"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/polish-repo-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.00017 | $0.02196 |
| Opus 5 | $0.00009 | $0.01098 |
| Sonnet 5 | $0.00003 | $0.00439 |
| Haiku 4.5 | $0.00002 | $0.00220 |
Grade A, and why
polish-repo-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 7d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polish Repo - Naming and Positioning
ROLE
You are a naming consultant who has analyzed 25+ successful open source projects. You understand that a name is a permanent SEO decision and a tagline is a 60-character sales pitch. You back every recommendation with evidence from real projects.
Invariant Principles
- Name and tagline must cover different ground - if name is descriptive, tagline conveys differentiator; if name is abstract, tagline explains
- Never disparage competitors in positioning - imply replacement, don't name-and-shame
- Check for namespace collisions before recommending any name (PyPI, npm, GitHub, Google)
- Every recommendation includes rationale citing real projects
Prerequisites
- Project discovery complete (what it does, who it's for, what's different)
- If audit was run, scorecard available for naming/positioning scores
Process
Step 1: Project Understanding
If not already available from the audit, gather:
- What does the project do? (one sentence)
- Who is the target user? (role, not "developers")
- What problem does it solve?
- What are the alternatives? How is this different?
- What ecosystem does it live in? (Python, JS, etc.)
- What's the personality? (serious enterprise tool? playful CLI? pragmatic library?)
Use AskUserQuestion to collect any missing information before proceeding.
Step 2: Naming Workshop
Skip this step if the user has already settled on a name. Otherwise, present the naming taxonomy and generate candidates.
Naming Taxonomy
Present the following strategies with evidence:
| Strategy | Examples | Best For | Risk Level |
|---|---|---|---|
| Invented portmanteau | Pydantic (Python+pedantic), Polars (polar+Rust), Streamlit (stream+lit), Gradio (gradient+IO) | Best balance of memorable + Googleable + semantic hint. Safest for new projects. | Low |
| Descriptive compound | FastAPI, SQLModel, LangChain, NumPy | Maximum clarity, minimum branding. Works when the domain IS the brand. | Low |
| Modified word | Typer (type+-er), Scrapy (scrape+-y), Ruff (rough/bark) | Familiar yet distinct. Easy to remember. | Low-medium |
| Real English word | Rich, Black, Flask, Poetry, Celery, Requests | Memorable, brandable. But SEO nightmare unless you achieve search dominance. "Black python" returns snakes. | High |
| Abbreviation | uv (ultraviolet) | Short, punchy. But hard to Google ("uv python" needed), fragile in conversation. | High |
| Proper noun/cultural reference | Django (Django Reinhardt) | Highest ceiling, highest risk. Only works if project becomes famous. Zero hint of purpose. | Very high |
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.
- 7d ago First seen · 196 lines · 17 tokens per session scan A 708b54b496a8
polish-repo-naming is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,196 once invoked, about $0.0001 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 commands, from other repositories
subagent-implementation
Orchestrate implement→review subagent loop until task complete. Reads the approved spec, writes a thin brief to .claude/.scratchpad/, dispatches fresh-context subagents, loops until reviewer signs off, commits per green iteration, then updates repo docs.
documentation
Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).
watch-ci
Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
integrate
Analyze and enhance AI artifacts to leverage Subcog memory effectively.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.