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/cyperx84/claude-code-plugin-examples/test-pattern-librarynpx skills add cyperx84/claude-code-plugin-examples --skill test-pattern-librarygit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWhat 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.00028 | $0.03440 |
| Opus 5 | $0.00014 | $0.01720 |
| Sonnet 5 | $0.00006 | $0.00688 |
| Haiku 4.5 | $0.00003 | $0.00344 |
Grade A, and why
Test Pattern Library 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 yesterday.
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 — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Pattern Library
Purpose
Provide battle-tested patterns for:
- Unit testing (functions, classes, modules)
- Integration testing (APIs, databases, services)
- End-to-end testing (user workflows)
- Test organization and structure
- Mocking and stubbing strategies
- Test data management
When to Use
Invoke this skill when:
- Writing tests for new code
- Improving test coverage
- Refactoring existing tests
- Teaching testing best practices
- Setting up testing infrastructure
- Debugging flaky tests
Instructions
Step 1: Identify Test Type
Determine what needs testing:
- Unit Test: Single function/method/class
- Integration Test: Multiple components working together
- E2E Test: Complete user workflow
- Snapshot Test: UI/output comparison
- Performance Test: Speed/load testing
Step 2: Choose Testing Framework
Select the appropriate framework:
- JavaScript/TypeScript: Jest, Vitest, Mocha, Jasmine
- Python: pytest, unittest
- Go: testing package
- Rust: built-in test framework
- Java: JUnit, TestNG
Step 3: Apply AAA Pattern
Structure tests with:
- Arrange: Set up test data and dependencies
- Act: Execute the code being tested
- Assert: Verify expected outcomes
Step 4: Include Edge Cases
Test for:
- Happy path (normal operation)
- Edge cases (boundary conditions)
- Error conditions (failures, exceptions)
- Null/undefined/empty values
- Invalid inputs
Testing Patterns
JavaScript/TypeScript (Jest/Vitest)
Unit Test Pattern
import { ${functionName} } from './${moduleName}';
describe('${functionName}', () => {
// Happy path
it('should ${expectedBehavior} when given valid input', () => {
// Arrange
const input = ${validInput};
const expected = ${expectedOutput};
// Act
const result = ${functionName}(input);
// Assert
expect(result).toBe(expected);
});
// Edge cases
it('should handle empty input', () => {
const result = ${functionName}('');
expect(result).toBe(${emptyResult});
});
it('should handle null input', () => {
const result = ${functionName}(null);
expect(result).toBeNull();
});
// Error conditions
it('should throw error for invalid input', () => {
expect(() => ${functionName}(${invalidInput}))
.toThrow('${expectedErrorMessage}');
});
});
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.
- yesterday First seen · 579 lines · 28 tokens per session scan A f258fe56b219
Test Pattern Library is a skill published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 28 tokens to every session and 3,440 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-08-31.
Other skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后,主动执行此流程! 将学到的经验归档为 skill,供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.