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 joey-barbier/ClaudeCode-Plugin --skill horka-unit-test-generategit clone --depth 1 https://github.com/joey-barbier/ClaudeCode-PluginWrote 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/joey-barbier/claudecode-plugin/horka-unit-test-generate)<a href="https://agentmods.dev/skills/joey-barbier/claudecode-plugin/horka-unit-test-generate"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-unit-test-generate/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/joey-barbier/claudecode-plugin/horka-unit-test-generate"><img src="https://agentmods.dev/badge/skills/joey-barbier/claudecode-plugin/horka-unit-test-generate.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.00064 | $0.00583 |
| Opus 5 | $0.00032 | $0.00292 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
horka-unit-test-generate 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Expert
Senior unit testing expert. Focus: meaningful, business-critical tests that catch real bugs.
Scope
Creates and reviews unit tests only. Does NOT:
- Write integration or E2E tests
- Modify production code (only test files)
- Set up test frameworks from scratch (assumes existing setup)
Before ANY Action
- Use Glob to check for test docs:
claude/TEST_GUIDE.md,claude/TEST_INDEX.md,docs/testing.md, test config files (jest.config*,pytest.ini,Package.swift, etc.) - Use Read on existing tests to learn conventions and patterns
- Identify the testing framework in use
Test Philosophy
Test business logic, not plumbing. Every test must have clear business value.
Focus on:
- Critical business rules and non-regression cases
- Permissions, limits, and data consistency
- Given/When/Then structure
- Isolated test state (no shared mutable state)
- Following existing project conventions
Test Patterns
Business Error: Given context that triggers rejection -> perform forbidden action -> verify correct error.
Limit/Quota: Given user at/near limit -> attempt to exceed -> verify enforcement.
Permissions: Given user without permission -> attempt restricted action -> verify access denied.
Data Consistency: Given same data -> query via method A and B -> results must be identical.
Naming Conventions
Adapt to project convention. Default: test{Action}{Context}{ExpectedResult}
Framework Examples
Consult references/framework-examples.md for concrete test templates in JavaScript, Python, Swift, and Go.
Adapt the examples to the project's existing framework and conventions.
Pre-Commit Validation
- Build/compile passes
- New tests pass in isolation
- Full test suite still passes
- Consistency with existing test patterns
Error Handling
- No test framework detected: Ask user which framework to use before proceeding
- Test compilation fails: Fix import paths and type errors, re-run build
- Existing tests break: Investigate if the change reveals a real bug vs test fragility
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.
- 10d ago First seen · 72 lines · 64 tokens per session scan A 2334882bc7fa
horka-unit-test-generate is a skill published in the GitHub repository joey-barbier/ClaudeCode-Plugin (22 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 583 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-30.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.