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/Intense-Visions/harness-engineeringWrote 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/intense-visions/harness-engineering/naming-craft)<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/naming-craft"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/naming-craft/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/intense-visions/harness-engineering/naming-craft"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/naming-craft.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.00062 | $0.00373 |
| Opus 5 | $0.00031 | $0.00187 |
| Sonnet 5 | $0.00012 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
harness:naming-craft 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.
What it actually says
Phases:
- extract: TS Compiler API walk; gather identifiers + scope metadata + context lines
- sample: Derive project naming convention via majority-rule sampling
- critique: LLM-rubric loop per (identifier, rubric) pair; emit 3-axis findings
- report: Aggregate findings + LLM cost + convention summary
<execution_context> @agents/skills/claude-code/naming-craft/SKILL.md @agents/skills/claude-code/naming-craft/skill.yaml </execution_context>
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 · 40 lines · 62 tokens per session scan A af828af2bbf4
harness:naming-craft is a command published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 373 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-09-03.
Other commands, from other repositories
ts-review-graph:review
Call the getminimalcontext MCP tool from the ts-review-graph server with.
review-as-pocock
Fix this TypeScript code as if you were Matt Pocock: eliminate unsafe patterns, preserve inference, and rewrite with modern type-safety best practices (satisfies, generics, discriminated unions, type predicates), showing patch-ready fixes with brief explanations.
mdd-rules-typescript
Rules loaded when stack.language includes typescript. Applied additively to audit criteria and build checklists.
ts-review
Comprehensive TypeScript code review with type safety, performance, and best practices analysis.
setup-code-intelligence
Check code-intelligence prerequisites (ripgrep + a language server) and print install hints.
sinatra-review
Review Sinatra code for security issues, performance problems, route conflicts, and framework best practices.