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/rohitg00/skillkit/test-patternsnpx skills add rohitg00/skillkit --skill test-patternsgit clone --depth 1 https://github.com/rohitg00/skillkitWhat 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.00138 | $0.01668 |
| Opus 5 | $0.00069 | $0.00834 |
| Sonnet 5 | $0.00028 | $0.00334 |
| Haiku 4.5 | $0.00014 | $0.00167 |
Grade A, and why
test-patterns 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 2d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Patterns
You are applying proven testing patterns to write maintainable, reliable tests. These patterns help ensure tests are readable, focused, and trustworthy.
Pattern Selection Guide
Use this to choose the right pattern for your situation:
- Structuring a single test? → Arrange-Act-Assert (AAA) or Given-When-Then
- Writing behavior/feature specs? → Given-When-Then (BDD style)
- Repeating test setup data? → Test Data Builders
- Many variations of complex objects? → Object Mother
- Testing same logic with many inputs? → Parameterized Tests
- Shared setup/teardown across tests? → Test Fixtures
- Verifying a dependency was called? → Spy
- Replacing an external dependency? → Test Doubles (Stub / Mock / Fake)
Pattern Combination Workflows
Patterns rarely stand alone — here's how to combine them for common scenarios:
Unit tests (isolated logic): Fixtures for setup → AAA structure → Stubs/Mocks for dependencies → Parameterized Tests for multiple input cases
Integration tests (service + external dependencies): Fixtures for setup → AAA structure → Fakes for external services (e.g. in-memory DB) → Spies to verify interaction points
BDD / feature specs: Given-When-Then → Object Mother or Test Data Builders for scenario data → Fakes for infrastructure
High-variation logic (validators, calculators, formatters): Parameterized Tests → Test Data Builders to construct each case → AAA structure within each case
Core Pattern: Arrange-Act-Assert (AAA)
Structure every test with three distinct phases:
// Arrange - Set up test data and dependencies
const user = createTestUser({ role: 'admin' });
const service = new UserService(mockRepository);
// Act - Execute the code under test
const result = await service.updateRole(user.id, 'member');
// Assert - Verify the expected outcome
expect(result.role).toBe('member');
expect(mockRepository.save).toHaveBeenCalledWith(user);
Guidelines:
- Keep sections visually separated (blank lines or comments)
- Arrange should be minimal - only what's needed for this test
- Act should be a single operation
- Assert should verify one logical concept
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.
- 2d ago First seen · 269 lines · 138 tokens per session scan A b47d6eaa1420
test-patterns is a skill published in the GitHub repository rohitg00/skillkit (1,477 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 138 tokens to every session and 1,668 once invoked, about $0.0007 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-30.
Other skills, from other repositories
Code Review Checklist
Runs a systematic checklist review on any code diff or file, covering correctness, security, performance, and readability.
code-review
AI-powered code review and PR analysis. Performs systematic reviews covering security vulnerabilities, code quality, style compliance, architectural integrity, test coverage, and performance considerations. Works with PR diffs, commit ranges, file changes, or raw code snippets. Primary keyword clusters: AI code review…
aap-lint
Skill "aap-lint" from automateyournetwork/netclaw, covering ansible lint operations, mcp server, available tools (9), key concepts and workflow: pre-deployment playbook validation.
code-review
Performs thorough code reviews with focus on best practices, security, performance, and maintainability. Use this skill when reviewing pull requests, auditing code quality, or getting feedback on implementations.
init-workspace-patterns
Extract code patterns.
workflows-create
Create a durable Zapier workflow from natural language using @zapier/zapier-durable and the Zapier SDK CLI. Use when the user wants to build a Zapier workflow, create an automation, write a durable workflow, build me a Zap that, create a durable that, or automate a multi-step process involving Zapier-connected apps.