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 agentmods add skills/knowhowlab/agent-testkit/test-initnpx skills add knowhowlab/agent-testkit --skill test-initgit clone --depth 1 https://github.com/knowhowlab/agent-testkitWhat 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 | $0.00102 | $0.01197 |
| Opus 5 | $0.00051 | $0.00598 |
| Sonnet 5 | $0.00020 | $0.00239 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
test-init 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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-init — Generate the project's test plans
Goal: Produce two reviewable, versioned plan files at the repository
root — TESTS_E2E.md (consumed by the test-e2e skill) and
TESTS_MANUAL.md (consumed by test-manual) — that together cover the
project's acceptance surface. Both follow plan format v1: read
references/plan-format.md in this skill's directory before writing
anything, and references/coverage-map.md before the recon.
Mode detection
If TESTS_E2E.md or TESTS_MANUAL.md already exists at the repo root →
update mode. Otherwise → create mode. If the user's request names
only one of the two files, still keep the sibling in sync where coverage
overlaps (parity rule), but don't rewrite it wholesale.
Create mode
- Recon first, questions second. Work through the recon checklist in
references/coverage-map.md: task runners, build files, compose files, CI workflows, docs and quickstarts, existing test trees, health endpoints, previous protocol files. Read; do not execute the stack. - Draft the coverage arc. Map findings onto the universal arc (gates → build → static validation → live → verification → failure/recovery → matrix → lifecycle → packaging → teardown → wrap-up). Note per phase whether it belongs in E2E, MANUAL, or both.
- Interview. One batched message with only the questions recon couldn't answer (the list is in coverage-map.md): canonical commands, known flakes → Facts, credentials pointer, manual-only vs e2e-only flows, wanted scopes, destructive fences, flaky external dependencies. Wait for answers.
- Write both files per the format contract. Non-negotiables:
- Every step has a concrete
Expect:— no "run it and see". - Same phase numbers where the two files cover the same ground; mode-exclusive phases appended after the shared ones.
- E2E steps are fully assertable by a machine; MANUAL steps are one
action each, copy-paste-ready, with GUI actions as
Do:lines. - Secrets never inline — pointers to where they live.
- Known caveats and flakes land under
## Factsso executors won't "fix" expected behavior. - Long commands become helper scripts under
tests/manual/helpers/, listed as Fixtures. - Stamp the marker comment:
<!-- agent-testkit plan · format v1 · generated YYYY-MM-DD by test-init -->.
- Every step has a concrete
- Static sanity pass. Verify every file, script, and path the plans
reference actually exists, and every command's binary is plausibly
available (
command -v, manifest inspection). Fix the plans, not the repo. Do not start services. - Report. Show the user: phases per file, scopes defined, Facts
recorded, anything you could not determine (marked
TODO(user)in the plan). Recommend a first run:test-manualonce by hand to shake out the plan, thentest-e2efor regressions.
What ships with it
2 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.
- yesterday First seen · 92 lines · 102 tokens per session scan A 4683deca5cf4
test-init is a skill published in the GitHub repository knowhowlab/agent-testkit (3 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,197 once invoked, about $0.0005 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.