Borrowing it
Nothing to install: this file belongs to kentcdodds/kody. 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/kentcdodds/kody/main/.agents/skills/testing-multi-worker-dev/SKILL.mdgit clone --depth 1 https://github.com/kentcdodds/kodyWrote 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/kentcdodds/kody/testing-multi-worker-dev)<a href="https://agentmods.dev/skills/kentcdodds/kody/testing-multi-worker-dev"><img src="https://agentmods.dev/badge/skills/kentcdodds/kody/testing-multi-worker-dev/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/kentcdodds/kody/testing-multi-worker-dev"><img src="https://agentmods.dev/badge/skills/kentcdodds/kody/testing-multi-worker-dev.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.00071 | $0.01690 |
| Opus 5.5 | $0.00028 | $0.00676 |
| Sonnet 5.5 | $0.00014 | $0.00338 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
testing-multi-worker-dev scanned grade A with 1 finding 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 21d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
terminal files or curl 3742 as a substitute. The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 21d ago Changed · -2 lines c794cc89d5c0
- 29d ago Changed · -2 lines 234e9dab1b27
- 1mo ago Changed · +6 lines b892d1822256
- 1mo ago Changed · +5 lines 5a469c3a93cd
- 1mo ago Changed · +6 lines b42c293c2423
- 1mo ago Changed · +3 lines f35406486d96
- 2mo ago First seen · 95 lines · 71 tokens per session scan A 1cbe654beb5a
testing-multi-worker-dev is a skill published in the GitHub repository kentcdodds/kody (805 stars, last pushed 13d ago), with no licence file. It adds 71 tokens to every session and 1,690 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
e2e-test
Design, maintain, and execute reliable end-to-end tests for critical user journeys with Agent Browser as first choice for exploration and Playwright as the preferred code path for suites and CI. Use for E2E strategy, journey coverage, flaky test triage, artifact collection, CI gating, regression prevention, and…
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.