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/djrhails/dotfiles/codenamenpx skills add DJRHails/dotfiles --skill codenamegit clone --depth 1 https://github.com/DJRHails/dotfilesWhat 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 | $0.00050 | $0.00639 |
| Opus 5 | $0.00025 | $0.00319 |
| Sonnet 5 | $0.00010 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
codename 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 yesterday.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codename Generator
Suggest a codename for a project by applying a principled naming philosophy.
Process
-
Fetch the naming guide — use WebFetch to read
https://hails.info/writing/codenamesand extract the full naming philosophy. This is the source of truth for what makes a good codename. -
Understand the project — read key files (README, package.json, CLAUDE.md, main source files) to understand:
- What the project does
- Core abstractions and metaphors
- Target audience
- Key technical properties (e.g. durability, speed, isolation, orchestration)
-
Apply the naming rules from hails.info:
- Be suggestive, not descriptive — prefer
gatekeeperoveridentity-service - Cute names aid recall — and subtly imply fungibility
- No pop culture references — if it needs explanation, the suggestive benefit vanishes
- Separate marketing names from codenames — codenames serve internal technical purposes
- Use the trademark "suggestive" test — like Coppertone, Greyhound, Tesla: infer meaning without being directly descriptive
- Be suggestive, not descriptive — prefer
-
If the user provided a theme or constraint, weight suggestions toward it (e.g. "something referencing durability" or "nautical theme").
-
Generate 5-7 candidates — for each, provide:
- The name
- A one-line connection to the project (why it's suggestive)
- CLI ergonomics check: is it short, easy to type, unambiguous to spell?
- Conflicts check: is it already a well-known dev tool or product?
-
Apply the tattoo test to each candidate: if the project's scope evolves (gains features, handles new domains, changes direction), does the name still fit? A good codename suggests a quality or metaphor, not a specific implementation — so it survives scope changes. If the project later does something completely different and the name still works, it passes.
-
Recommend your top pick with a brief justification covering:
- How it passes the suggestive test
- How it passes the tattoo test (resilient to scope changes)
- Why it fits this specific project
- How it works in practice (
<name> deploy,<name> init, etc.)
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.
- yesterday First seen · 50 lines · 50 tokens per session scan A 366e016c1cef
codename is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 639 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
dustoff
Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives…