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 ckorhonen/hone-skills --skill test-naming-auditgit clone --depth 1 https://github.com/ckorhonen/hone-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/ckorhonen/hone-skills/test-naming-audit)<a href="https://agentmods.dev/skills/ckorhonen/hone-skills/test-naming-audit"><img src="https://agentmods.dev/badge/skills/ckorhonen/hone-skills/test-naming-audit/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/ckorhonen/hone-skills/test-naming-audit"><img src="https://agentmods.dev/badge/skills/ckorhonen/hone-skills/test-naming-audit.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.00066 | $0.01732 |
| Opus 5 | $0.00033 | $0.00866 |
| Sonnet 5 | $0.00013 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
hone:test-naming-audit 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 11d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Naming Audit
What This Skill Does
Scans test files across the codebase and evaluates whether each test method/function name communicates the behavior being verified. A good test name reads as a complete sentence: it states what is being tested, under what conditions, and what the expected outcome is.
Flags tests whose names are:
- Cryptic:
test1,test2,testA,testIt,foo_test. - Too short: Single-word names like
testParse,testLogin,testSavethat omit conditions and expectations. - Abbreviated:
testUsrAuth,test_inv_reqwhere abbreviations hurt readability. - Implementation-focused: Names that reference implementation details
rather than behavior (
testCallsApi,testUsesCache). - Numbered: Names using numeric suffixes to distinguish cases
(
testParse1,testParse2).
Reports each finding with the test name, file:line, the issue category, and a suggested improvement pattern.
When To Use
- On every PR that touches test files.
- As a weekly sweep of the full test suite.
- When the user asks to "audit test names" or "check test naming".
Do Not Use
- For test coverage analysis or missing tests.
- For test structure, assertions, or setup/teardown patterns.
- For non-test code naming — use
hone:intent-clarity-auditorhone:naming-specificity-auditinstead. - To rename tests automatically. This skill reports findings only.
Inputs To Confirm
- Scope: Which directories or file patterns to scan for tests (default:
auto-detect test directories and files matching common patterns like
*_test.*,*.test.*,*.spec.*,test_*.*,*Test.*,*Spec.*). - Exclusions: Glob patterns for files to skip (e.g., test helpers, fixtures, generated tests).
- Strictness:
standard(flag clearly bad names) orstrict(also flag names that are acceptable but could be more descriptive). Default:standard.
Instructions
- Find test files. Walk the repository tree and identify test files using
common naming conventions:
- Files:
*_test.go,*.test.ts,*.test.js,*.spec.ts,*.spec.js,test_*.py,*_test.py,*_test.rb,*Test.java,*Test.kt,*Spec.java,*Spec.kt,*_spec.rb,*Tests.swift,*_tests.rs. - Directories:
test/,tests/,__tests__/,spec/. Apply user exclusions.
- Files:
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.
- 11d ago First seen · 160 lines · 66 tokens per session scan A 1cca44cda9ae
hone:test-naming-audit is a skill published in the GitHub repository ckorhonen/hone-skills (0 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 1,732 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
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
Biome
Biome 2.x — fast all-in-one web toolchain in Rust. Formats, lints, assists. Replaces Prettier + ESLint.
biome
Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint).
vibe-check
Audit code for "vibe coding sins" — patterns that indicate AI-generated code was accepted without proper review. Produces a scored report card with fix suggestions.
ruff-docs
Ruff — fast Python linter and formatter in Rust. 900+ rules, Black-compatible formatter, LSP, CI/CD.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.