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 acolomba/pi-claude-marketplace --skill typescript-unit-testsgit clone --depth 1 https://github.com/acolomba/pi-claude-marketplaceWrote 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/acolomba/pi-claude-marketplace/typescript-unit-tests)<a href="https://agentmods.dev/skills/acolomba/pi-claude-marketplace/typescript-unit-tests"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/typescript-unit-tests/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/acolomba/pi-claude-marketplace/typescript-unit-tests"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/typescript-unit-tests.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.00065 | $0.00503 |
| Opus 5.5 | $0.00026 | $0.00201 |
| Sonnet 5.5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
typescript-unit-tests 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 7d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript unit tests
Every case must discriminate the behavior named in its title: a wrong implementation makes the assertion fail. A test with weak assertions costs all the maintenance of a test and gives none of the protection. A planned case names the behavior it proves; a verified case would fail if that behavior broke.
In the rules files, "Do" and "Do not" are hard rules. "Prefer" states the default and allows a justified exception. "May" grants a permission.
Use node:test for the runner, lifecycle, and the context's t.mock; node:assert/strict for assertions; strong-mock for strict interaction mocks; --experimental-test-coverage for coverage. Do not add another runner, assertion library, or mocking library.
Read before you act
| When you | Read |
|---|---|
| plan, add, move, or rename a source or test module | .agents/skills/typescript-unit-tests/rules/pairing-and-design.md |
| write the imports of a test module | .agents/skills/typescript-unit-tests/rules/tools.md |
| write or change a test case | .agents/skills/typescript-unit-tests/rules/cases.md |
use a fake, a spy, or a strong-mock mock |
.agents/skills/typescript-unit-tests/rules/test-doubles.md |
| test a type-only module, a barrel, the filesystem, HTTP, time, env, or an adapter contract | .agents/skills/typescript-unit-tests/rules/boundaries.md |
| review a case or a source-test pair, or classify a finding | .agents/skills/typescript-unit-tests/rules/review.md |
| run tests or decide which checks a task needs | .agents/skills/local-verification/SKILL.md |
What ships with it
6 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.
- 7d ago Changed 5dd5c3673721
- 15d ago First seen · 29 lines · 65 tokens per session scan A 1db3f154a5d1
typescript-unit-tests is a skill published in the GitHub repository acolomba/pi-claude-marketplace (28 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 503 once invoked, about $0.0003 per session on Opus 5.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-10-15.
Other skills, from other repositories
typescript
TypeScript strict mode with eslint and jest.
jest-unit
Unit testing skill using Jest for TypeScript and JavaScript, covering mocking, spies, snapshots, coverage, async testing, and custom matchers.
Jasmine Testing
BDD-style JavaScript testing with Jasmine covering spies, async patterns, custom matchers, clock manipulation, and comprehensive test organization for frontend and Node.js applications.
vitest-skill
Generates Vitest tests in JavaScript/TypeScript with Vite-native speed. Jest-compatible API with ESM support and HMR. Use when user mentions "Vitest", "vi.mock", "vitest.config". Triggers on: "Vitest", "vi.mock", "vi.fn", "Vite test", "vitest config".
jest
Jest testing best practices for JavaScript and TypeScript applications, covering test structure, mocking, and assertion patterns.
typescript-testing
Applies repository-aware TypeScript test design, behavior evidence, isolation, and mock-boundary criteria. Use when writing or reviewing unit tests.