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 hamr0/agentic-toolkit --skill test-generategit clone --depth 1 https://github.com/hamr0/agentic-toolkitWrote 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/hamr0/agentic-toolkit/test-generate)<a href="https://agentmods.dev/skills/hamr0/agentic-toolkit/test-generate"><img src="https://agentmods.dev/badge/skills/hamr0/agentic-toolkit/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/hamr0/agentic-toolkit/test-generate"><img src="https://agentmods.dev/badge/skills/hamr0/agentic-toolkit/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.00011 | $0.00734 |
| Opus 5 | $0.00005 | $0.00367 |
| Sonnet 5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
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 3d 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.
This is a copy
100% identical to test-generate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate tests for $ARGUMENTS, then run them. This is a generate → run → verify loop, not just file generation.
1. Discover
- Detect the test framework already in use (look for
jest.config*,vitest.config*,pytest.ini/pyproject.toml [tool.pytest], Go's_test.goconvention,Cargo.toml [dev-dependencies], etc.). Never add a new framework or runner. - Skim 1–2 existing test files near the target to mirror style, fixtures, setup/teardown, assertion style, and naming convention.
2. Generate
Cover:
- Happy path (expected usage)
- Edges (empty / null / boundary / malformed)
- Errors (invalid input, IO / network / DB failures)
Match existing patterns:
- Same framework, same fixture style, same naming convention.
- Reuse existing setup/teardown helpers; do not add new mock libraries or new test-runner config.
- Do not add test-only public methods or exports to production code to make a test possible — if the test wants a hook the prod code doesn't expose, stop and ask.
3. Run
Execute the project's real test command, scoped to just the new tests
(-t <name>, --testPathPattern, pytest path/to/test.py, go test ./pkg, etc.). Report:
- Pass / fail counts.
- Any failure with the assertion message and
file:line.
4. Verify the tests BITE
A test that passes is not the same as a test that exercises the code. For each new test, confirm:
- It would fail if the function under test returned the wrong value. Mentally swap a broken impl — does the assertion actually catch it?
- It isn't
expect(true).toBe(true),expect(fn).toBeDefined(), or a mock asserting itself. - It isn't passing only because the setup masked the real call.
Mark each new test biting or superficial (with reason). Superficial tests count as a failure to ship — either fix or delete.
5. Report
- Files added / modified.
- Pass / fail.
- Biting vs superficial breakdown.
- What was deliberately not tested, and why (third-party shims, trivial getters/setters, generated code). Documented gaps beat fake coverage.
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.
- 3d ago First seen · 68 lines · 11 tokens per session scan A 6696cdf94880
test-generate is a skill published in the GitHub repository hamr0/agentic-toolkit (22 stars, last pushed 4d ago), licensed Apache-2.0. It adds 11 tokens to every session and 734 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-generate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
layer-testing
Generate comprehensive tests for architectural layers with coverage-first analysis. Use when testing specific layers (core, domain, application, infrastructure, boundary). Reads testing strategy from playbook or uses interactive template selection.
verify-no-regressions
Verify no behavioral regressions after implementation. Spawns parallel subagents for semantic diff review + test execution. Use when: user says "verify no regressions", "check for regressions", "make sure nothing broke".
await-merge
Wait for a PR's checks, merge it with linear history, update the local base branch.
phone-harness
Control the user's phone — iPhone through the Mac's iPhone Mirroring window, or an Android over adb: open apps, tap, type, swipe, read the screen.
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.