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 oborchers/fractional-cto --skill naming-precisiongit clone --depth 1 https://github.com/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/naming-precision)<a href="https://agentmods.dev/skills/oborchers/fractional-cto/naming-precision"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/naming-precision/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/oborchers/fractional-cto/naming-precision"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/naming-precision.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.00063 | $0.02542 |
| Opus 5.5 | $0.00025 | $0.01017 |
| Sonnet 5.5 | $0.00013 | $0.00508 |
| Haiku 4.5 | $0.00006 | $0.00254 |
Grade A, and why
naming-precision 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A Name Must Be the Most Precise Word Available
If a reader has to look at the implementation to understand what a variable holds, the name has failed. A precise name eliminates the need for comments, reduces cognitive load during reviews, and prevents an entire category of bugs where the wrong variable is used because two names were too similar or too vague. This is not about taste. This is about whether your code communicates or obfuscates.
Banned Names
The following names are prohibited in any scope wider than a single expression. They tell the reader nothing. They are placeholders left behind by someone who did not finish thinking.
| Banned | Why | What to Use Instead |
|---|---|---|
data |
Everything is data | userProfiles, invoiceLineItems, sensorReadings |
info |
Synonym for data, equally useless | accountDetails, shippingAddress, errorContext |
temp |
What is temporary about it? | unsavedDraft, pendingUpload, swapBuffer |
result |
Result of what? | validationErrors, searchMatches, parsedConfig |
value |
Value of what? | discountPercent, temperatureCelsius, pixelWidth |
item |
Item in what collection? | cartProduct, logEntry, notificationPayload |
thing |
Not a word that belongs in code | Name the actual concept |
handle |
Verb pretending to be a noun | fileDescriptor, connectionSocket, eventCallback |
process |
What does it process? How? | validatePayment, compressImage, routeIncomingRequest |
manager |
Manages what? How? | connectionPool, cacheEvictor, taskScheduler |
helper |
Helping with what? | Name the actual operation: formatCurrency, retryWithBackoff |
utils |
Junk drawer | Split into specific modules: dateFormatting, stringValidation |
misc |
Admission of organizational failure | Categorize properly or inline the code |
Zero tolerance. If you see any of these names in a review, reject the code. No exceptions. No "but it's obvious from context." Context changes. Names stay.
What ships with it
1 file 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 · 220 lines · 63 tokens per session scan A 19e9e187c132
naming-precision is a skill published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 2,542 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…