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/porcupine-md/jonggrang/unit-testing-patternsnpx skills add porcupine-md/jonggrang --skill unit-testing-patternsgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/unit-testing-patterns)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/unit-testing-patterns"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/unit-testing-patterns.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00022 | $0.00837 |
| Opus 5 | $0.00011 | $0.00418 |
| Sonnet 5 | $0.00004 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
unit-testing-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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The AAA Pattern
Every test follows Arrange-Act-Assert:
it('creates a user with hashed password', async () => {
// ARRANGE — set up inputs and mocks
const dto = { email: '[email protected]', password: 'plaintext' };
const mockRepo = { save: vi.fn().mockResolvedValue({ id: '1', ...dto }) };
const service = new UserService(mockRepo);
// ACT — call the thing under test
const user = await service.createUser(dto);
// ASSERT — verify the outcome
expect(user.id).toBe('1');
expect(mockRepo.save).toHaveBeenCalledWith(
expect.objectContaining({ email: dto.email })
);
expect(mockRepo.save.mock.calls[0][0].password).not.toBe('plaintext');
});
What to Mock
Mock: External I/O — database, network, filesystem, timers, random values
Don't mock: Pure functions, your own business logic, constants
// GOOD: mock the database (I/O)
vi.mock('./db', () => ({ findUser: vi.fn() }));
// BAD: mock your own service (you'd be testing the mock, not the code)
vi.mock('./userService');
Mocking Strategies
Spies (observe without replacing)
const logSpy = vi.spyOn(console, 'error').mockImplementation(() => {});
// ... do something
expect(logSpy).toHaveBeenCalledWith(expect.stringContaining('Error'));
logSpy.mockRestore();
Stubs (replace with controlled value)
const getTimeSpy = vi.spyOn(Date, 'now').mockReturnValue(1234567890);
Module mocks
vi.mock('./email-service', () => ({
sendEmail: vi.fn().mockResolvedValue({ success: true }),
}));
Test Isolation
describe('UserService', () => {
let service: UserService;
let mockRepo: ReturnType<typeof createMockRepo>;
beforeEach(() => {
// Fresh instance per test — no shared state
mockRepo = createMockRepo();
service = new UserService(mockRepo);
});
afterEach(() => {
vi.clearAllMocks();
});
});
Assertion Best Practices
// Be specific — assert exact values when meaningful
expect(result.count).toBe(3); // not toBeTruthy()
// Use asymmetric matchers for dynamic values
expect(result).toEqual(expect.objectContaining({
id: expect.any(String),
createdAt: expect.any(Date),
name: 'Alice',
}));
// Test error type specifically
await expect(service.delete('nonexistent')).rejects.toThrow(NotFoundError);
// Don't over-assert (don't test internals)
// BAD: testing private method was called
// GOOD: testing the public observable outcome
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 · 141 lines · 22 tokens per session scan A 6a5dfb6ac9d3
unit-testing-patterns is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 837 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…