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 s977043/river-review --skill code-unit-ts-jestgit clone --depth 1 https://github.com/s977043/river-reviewWrote 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/s977043/river-review/code-unit-ts-jest)<a href="https://agentmods.dev/skills/s977043/river-review/code-unit-ts-jest"><img src="https://agentmods.dev/badge/skills/s977043/river-review/code-unit-ts-jest.svg" alt="Measured on agentmods" 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.00023 | $0.00723 |
| Opus 5 | $0.00012 | $0.00362 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
Unit Test Scaffold (TypeScript) 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 4d 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.
What it actually says
Pattern declaration
Primary pattern: Generator Secondary patterns: Inversion Why: 仕様書からTypeScriptユニットテストの足場を生成するジェネレーターであり、仕様の抜けをテスト観点から逆照射する。
Role
あなたは熟練したTypeScript開発者です。 仕様書の内容を満たすための「単体テストのスケルトンコード（足場）」を作成してください。実装は行わず、テスト構造のみを作成します。
Non-goals / 扱わないこと
- 実装ロジックや最適化方針は記述しない。
- E2E/統合テストの網羅は対象外で、Jest/Vitest 向けのユニットテスト足場に限定する。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分に仕様書（
docs/**/*.mdまたはspecs/**/*.md）が含まれている - 仕様書にTypeScriptアプリケーションに関する記述がある
- inputContextにfullFileが含まれている
ゲート不成立時の出力: NO_REVIEW: code-unit-ts-jest — 対象となるTypeScript仕様が差分に含まれていない
False-positive guards / 抑制条件
- 仕様に明記されていない要件を推測で追加しない。
- 対象外とされた領域（例: 外部サービス接続の実装詳細）への指摘は行わない。
Output Format
TypeScript (Jest/Vitest) のコードブロック。
describe で機能をグルーピングし、it または test で各ケースを定義します。
各 it ブロックの中には、検証すべき内容をコメントで // TODO: ... として記述してください。
Example
describe('UserRegistration', () => {
describe('validation', () => {
it('should throw error when email is invalid', async () => {
// TODO: Arrange invalid email input
// TODO: Act call registration
// TODO: Assert ValidationError
});
});
});
Constraints
- 実装の詳細（DOM操作など）には立ち入らず、インターフェースの入出力と振る舞いに注目してください。
- エッジケース（空入力、最大長、不正文字）のテストケースを必ず含めてください。
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.
- 4d ago First seen · 73 lines · 23 tokens per session scan A 112cf3dddf75
Unit Test Scaffold (TypeScript) is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 723 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
JavaScript Testing Patterns
Modern JavaScript testing strategies with Jest, Mocha, and testing best practices covering unit testing, integration testing, mocking, async patterns, and DOM testing.
ts-library
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, configuring dual CJS/ESM output, or setting up release workflows.
jest-expert
Expert in Jest unit testing framework, mocks, snapshots, coverage reports, watch mode, and custom matchers. Use when the user mentions testing, unit testing, JavaScript, QA, mocking, or snapshots, or when the task involves Jest Framework, Test Structure, Advanced Features, or Basic Unit Tests.
typescript-testing
TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.
test-driven-development
Use when writing production code. Enforces RED-GREEN-REFACTOR cycle: write failing test, make it pass, improve design. Prevents test-after development and ensures verified behavior.
dhpk-pytest-async
Async pytest + pytest-asyncio testing: asynciomode=auto, SQLite fixtures, httpx.AsyncClient + ASGITransport, unit/integration split, coverage floor, live markers. Use when writing or reviewing async FastAPI/SQLAlchemy tests, or enforcing dhpk-tdd-workflow. Not for production code. Output: offline-green async tests.