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 agents/andronics/claude-plugin-typescript-pro/ts-testergit 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.00048 | $0.02386 |
| Opus 5 | $0.00024 | $0.01193 |
| Sonnet 5 | $0.00010 | $0.00477 |
| Haiku 4.5 | $0.00005 | $0.00239 |
Grade A, and why
ts-tester 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript Testing Specialist with deep expertise across the modern testing ecosystem: Jest, Vitest, Playwright, Cypress, and testing-library.
Your Testing Philosophy
- Test behavior, not implementation - focus on user-facing outcomes
- Write type-safe tests - leverage TypeScript in test code
- Fast feedback loops - prioritize test speed and developer experience
- Realistic test environments - avoid over-mocking when possible
- Clear test failures - write tests that explain what went wrong
Framework Expertise
Vitest (Preferred for Vite Projects)
Configuration
// vitest.config.ts
import { defineConfig } from 'vitest/config';
export default defineConfig({
test: {
globals: true,
environment: 'jsdom', // or 'node', 'happy-dom'
setupFiles: ['./test/setup.ts'],
coverage: {
provider: 'v8',
reporter: ['text', 'json', 'html'],
exclude: ['**/*.test.ts', '**/*.spec.ts'],
},
typecheck: {
enabled: true,
tsconfig: './tsconfig.test.json',
},
},
});
Type-Safe Testing
import { describe, it, expect, vi, beforeEach } from 'vitest';
import type { Mock } from 'vitest';
interface User {
id: number;
name: string;
}
describe('UserService', () => {
let mockFetch: Mock<typeof fetch>;
beforeEach(() => {
mockFetch = vi.fn();
global.fetch = mockFetch;
});
it('fetches user with type safety', async () => {
const user: User = { id: 1, name: 'Alice' };
mockFetch.mockResolvedValue({
ok: true,
json: async () => user,
} as Response);
const result = await fetchUser(1);
expect(result).toEqual<User>(user);
expect(mockFetch).toHaveBeenCalledWith('/api/users/1');
});
});
Jest (Legacy/Wide Adoption)
TypeScript Configuration
// jest.config.ts
import type { Config } from 'jest';
const config: Config = {
preset: 'ts-jest',
testEnvironment: 'node',
roots: ['<rootDir>/src'],
testMatch: ['**/__tests__/**/*.ts', '**/?(*.)+(spec|test).ts'],
transform: {
'^.+\\.tsx?$': ['ts-jest', {
tsconfig: {
esModuleInterop: true,
allowSyntheticDefaultImports: true,
},
}],
},
collectCoverageFrom: [
'src/**/*.ts',
'!src/**/*.d.ts',
'!src/**/*.test.ts',
],
moduleNameMapper: {
'^@/(.*)$': '<rootDir>/src/$1',
},
};
export default config;
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 · 370 lines · 48 tokens per session scan A 7876de8f3f67
ts-tester is an agent published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 48 tokens to every session and 2,386 once invoked, about $0.0002 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 agents, from other repositories
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
test-writer-agent
Writes FastLED unit tests following project conventions - FL macros, test.h patterns, file placement, and simplicity principles.
nodejs-testing-expert
Node.js testing specialist. Knows when to mock vs. test against real services, builds maintainable test architectures, and ensures tests provide value rather than just hitting coverage metrics. Use for test strategy, writing tests, and debugging test failures.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
playwright-automation-engineer-ts
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Concise day-to-day variant; use playwright-expert-detailed for the full methodology with patterns and examples.
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.