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/andronics/claude-plugin-typescript-pro/test-generatornpx skills add andronics/claude-plugin-typescript-pro --skill test-generatorgit clone --depth 1 https://github.com/andronics/claude-plugin-typescript-proWhat 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.00064 | $0.02810 |
| Opus 5 | $0.00032 | $0.01405 |
| Sonnet 5 | $0.00013 | $0.00562 |
| Haiku 4.5 | $0.00006 | $0.00281 |
Grade A, and why
test-generator 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.
How it starts
The opening of the file, as written. The whole thing — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript Test Generation Specialist that creates comprehensive, type-safe tests across all testing frameworks.
When to Activate
Automatically activate when detecting:
- New code without tests
- Modified code needing test updates
- Low test coverage areas
- Complex functions requiring thorough testing
- API endpoints needing integration tests
- UI components needing component tests
- User flows requiring E2E tests
- Type definitions needing type tests
- Refactored code needing regression tests
Framework Detection
Automatically detect and use the appropriate framework:
Check package.json dependencies:
vitest→ Vitestjest,@jest/globals→ Jest@playwright/test→ Playwrightcypress→ Cypress@testing-library/react→ React Testing Library@testing-library/vue→ Vue Testing Library
Check for config files:
vitest.config.ts→ Vitestjest.config.ts/js→ Jestplaywright.config.ts→ Playwrightcypress.config.ts→ Cypress
Unit Test Generation
Vitest/Jest Tests
For Pure Functions:
// Source: src/utils/math.ts
export function add(a: number, b: number): number {
return a + b;
}
export function divide(a: number, b: number): number {
if (b === 0) {
throw new Error('Division by zero');
}
return a / b;
}
Generated Test:
// Test: src/utils/math.test.ts
import { describe, it, expect } from 'vitest';
import { add, divide } from './math';
describe('math utilities', () => {
describe('add', () => {
it('adds two positive numbers', () => {
expect(add(2, 3)).toBe(5);
});
it('adds negative numbers', () => {
expect(add(-2, -3)).toBe(-5);
});
it('adds zero', () => {
expect(add(5, 0)).toBe(5);
});
it('has correct type inference', () => {
const result: number = add(1, 2);
expect(result).toBe(3);
});
});
describe('divide', () => {
it('divides two positive numbers', () => {
expect(divide(10, 2)).toBe(5);
});
it('handles decimal results', () => {
expect(divide(5, 2)).toBe(2.5);
});
it('throws on division by zero', () => {
expect(() => divide(10, 0)).toThrow('Division by zero');
});
it('handles negative numbers', () => {
expect(divide(-10, 2)).toBe(-5);
expect(divide(10, -2)).toBe(-5);
});
});
});
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 · 407 lines · 64 tokens per session scan A caf391f2a523
test-generator is a skill published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 64 tokens to every session and 2,810 once invoked, about $0.0003 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
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
testing
Writing or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-flutter
Flutter App のテスト実行・静的解析・フォーマット・テスト記述ガイド.
test
Run tests. Use after code changes to validate. Arguments: unit (default, no GPU), e2e (with models), filter name, or all.