Borrowing it
Nothing to install: this file belongs to satanyakiv/NutriSport. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/satanyakiv/NutriSport/main/.claude/skills/gen-test/SKILL.mdgit clone --depth 1 https://github.com/satanyakiv/NutriSportWrote 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/satanyakiv/nutrisport/gen-test)<a href="https://agentmods.dev/skills/satanyakiv/nutrisport/gen-test"><img src="https://agentmods.dev/badge/skills/satanyakiv/nutrisport/gen-test/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/satanyakiv/nutrisport/gen-test"><img src="https://agentmods.dev/badge/skills/satanyakiv/nutrisport/gen-test.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.00089 | $0.00775 |
| Opus 5 | $0.00044 | $0.00387 |
| Sonnet 5 | $0.00018 | $0.00155 |
| Haiku 4.5 | $0.00009 | $0.00077 |
Grade A, and why
gen-test 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate tests for: $ARGUMENTS
Context
This is a KMP project. Tests go in src/commonTest/kotlin/ mirroring source structure. The project uses kotlin.test, Turbine for Flows, Mokkery for mocking, assertk for assertions.
What to test by class type
| Type | What to test | Mocking | Flow testing |
|---|---|---|---|
| UseCase (pure) | invoke() success/error paths | Fake repository | No (unless returns Flow) |
| UseCase (with repo) | invoke() delegates correctly, error propagation | Fake repository | Turbine if returns Flow |
| ViewModel | State transitions (Loading→Content), error handling, user actions | Fake repos via constructor | Turbine for StateFlow |
| Mapper | Field mapping, edge cases (null, empty), enum conversion | None (pure functions) | No |
| Repository | DTO→Domain mapping, error wrapping | Mock data source | Turbine for Flow returns |
Process
- Read the source file to understand what to test
- Determine the class type (see table above) to pick the right testing approach
- Check for existing tests, fake data factories, and Fake repositories in the module's
commonTest - If ViewModel/UseCase test needs a Flow-based repository — create
Fake{Entity}RepositorywithMutableSharedFlow(see examples/fake-repository.kt) - Reference examples/usecase-test.kt for pure UseCase tests
- Reference examples/viewmodel-test.kt for ViewModel tests with Turbine
- Reference examples/mapper-test.kt for pure mapper tests
- For full recipes and pitfalls → see references/testing-patterns.md
- Create fake data factories (
fakeProduct(),fakeCustomer()) if not yet present - Write tests covering: happy path, error path, edge cases
- Run:
./gradlew :{module}:allTests --tests "*{TestClass}" - Verify all pass
Conventions
- Naming:
`should X when Y`backtick format - AAA pattern:
// Arrange→// Act→// Assertcomments - Flows: Always Turbine (
test { awaitItem() }) — never.first()or.toList() - Mocking: Mokkery —
every { },verify { },mock<Interface>() - Coroutines:
runTest+StandardTestDispatcher()+Dispatchers.setMain() - Assertions: assertk —
assertThat(x).isEqualTo(y),isInstanceOf<Type>() - Fakes: Prefer
Fake{Entity}Repositoryclasses over inlineobject : Interfacefor reuse - One assertion per test (or one logical group)
- No real I/O — mock everything external
What ships with it
4 files 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 · 49 lines · 89 tokens per session scan A 0e02c1817ba0
gen-test is a skill published in the GitHub repository satanyakiv/NutriSport (11 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 775 once invoked, about $0.0004 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.