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 VoDaiLocz/kilo-kit-mcp --skill testinggit clone --depth 1 https://github.com/VoDaiLocz/kilo-kit-mcpWrote 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/vodailocz/kilo-kit-mcp/testing)<a href="https://agentmods.dev/skills/vodailocz/kilo-kit-mcp/testing"><img src="https://agentmods.dev/badge/skills/vodailocz/kilo-kit-mcp/testing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.03045 |
| Opus 5 | $0.00030 | $0.01522 |
| Sonnet 5 | $0.00012 | $0.00609 |
| Haiku 4.5 | $0.00006 | $0.00304 |
Grade A, and why
testing-strategy 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.
How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧪 Testing Strategy Skill
Philosophy: If it's not tested, it's broken. You just don't know it yet.
When to Use
Use this skill when:
- Writing new code (TDD approach)
- Adding tests to existing code
- Improving test coverage
- Fixing flaky tests
- Setting up testing infrastructure
- Debugging test failures
Do NOT use this skill when:
- Just running existing tests
- Quick syntax check
The Testing Pyramid
╱╲
╱ ╲
╱ E2E╲ Few, slow, expensive
╱──────╲ Full system tests
╱ ╲
╱Integration╲ Medium amount
╱────────────╲ Component interaction
╱ ╲
╱ Unit Tests ╲ Many, fast, cheap
╱──────────────────╲ Single unit isolation
TDD Workflow: RED → GREEN → REFACTOR
Step 1: RED (Write Failing Test)
// Write the test BEFORE the implementation
describe('calculateDiscount', () => {
it('should apply 10% discount for orders over $100', () => {
// This test will FAIL because function doesn't exist yet
const result = calculateDiscount(150);
expect(result).toBe(135);
});
});
Run test → Should FAIL (RED)
Step 2: GREEN (Minimal Implementation)
// Write the MINIMUM code to pass the test
function calculateDiscount(amount: number): number {
if (amount > 100) {
return amount * 0.9;
}
return amount;
}
Run test → Should PASS (GREEN)
Step 3: REFACTOR (Improve)
// Improve code while keeping tests green
const DISCOUNT_THRESHOLD = 100;
const DISCOUNT_RATE = 0.1;
function calculateDiscount(amount: number): number {
if (amount > DISCOUNT_THRESHOLD) {
return amount * (1 - DISCOUNT_RATE);
}
return amount;
}
Run test → Should still PASS
Unit Testing Patterns
Basic Structure (AAA Pattern)
describe('UserService', () => {
describe('createUser', () => {
it('should create user with valid data', async () => {
// Arrange
const userData = { email: '[email protected]', name: 'Test' };
const mockRepo = { create: jest.fn().mockResolvedValue({ id: '1', ...userData }) };
const service = new UserService(mockRepo);
// Act
const result = await service.createUser(userData);
// Assert
expect(result.id).toBe('1');
expect(result.email).toBe(userData.email);
expect(mockRepo.create).toHaveBeenCalledWith(userData);
});
});
});
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 · 541 lines · 60 tokens per session scan A 18031de3d917
testing-strategy is a skill published in the GitHub repository VoDaiLocz/kilo-kit-mcp (26 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 3,045 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-09-03.
Other skills, from other repositories
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
test-pyramid
Decide what type of test to write, structure the suite, measure health, and apply test doubles correctly.
write-tests
Write Vitest unit/integration tests OR Playwright e2e tests for an existing source file (server action, page, component, query). Reads the project's wired test framework from .workflow/meta.json#stack.test, follows the mocking patterns already present in vitest.setup.ts and any sibling test files. Use when the user…
rn-write-tests
Use to write tests for an Expo + RN app: Jest + React Native Testing Library for unit/integration (components, hooks, queries, mutations) and Maestro for end-to-end flows (sign-in, navigation, forms). Sets up the testing stack on first call (jest-expo preset, RNTL, jest config) and writes a focused test next to the…
browser-automation
Browser automation powers web testing, scraping, and AI agent.
senior-qa
Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and…