ag-skills: Skill for Claude Code

.agent/skills/testing-patterns/SKILL.md

testing-patterns is a skill for Claude Code from duongnguyen321/ag-skills. It costs 16 tokens per session (840 once invoked), scanned A, original, no licence file.

Guidance on common software testing approaches, including unit tests, integration tests, and mocks. Unit tests check small pieces; integration tests check how parts work together.

In plain words
What is it for?
Use it to design testing strategies, write unit and integration tests, and decide when mocking is appropriate.
Why use it?
It helps choose suitable tests and avoid gaps caused by relying on only one testing method.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is duongnguyen321/ag-skills's own configuration. It tells Claude Code how to work on ag-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ag-skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to duongnguyen321/ag-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/duongnguyen321/ag-skills/main/.agent/skills/testing-patterns/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/duongnguyen321/ag-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for testing-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/duongnguyen321/ag-skills/testing-patterns.svg)](https://agentmods.dev/skills/duongnguyen321/ag-skills/testing-patterns)
Your own site
<a href="https://agentmods.dev/skills/duongnguyen321/ag-skills/testing-patterns"><img src="https://agentmods.dev/badge/skills/duongnguyen321/ag-skills/testing-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 840 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00840
Opus 5 $0.00008 $0.00420
Sonnet 5 $0.00003 $0.00168
Haiku 4.5 $0.00002 $0.00084

Measured 8d ago against content hash f229085ad979, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/test_runner.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agent/skills/testing-patterns/SKILL.md · 179 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 8d ago First seen · 179 lines · 16 tokens per session scan A f229085ad979

Subscribe to this mod's changes

testing-patterns is a skill published in the GitHub repository duongnguyen321/ag-skills (2 stars, last pushed 21d ago), with no licence file. It adds 16 tokens to every session and 840 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.

Related

Other skills, from other repositories

golang-testing

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…

samber/cc-skills-golang · 115 tokens

golang-stretchr-testify

Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…

samber/cc-skills-golang · 97 tokens

javascript-testing-patterns

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

rmyndharis/antigravity-skills · 63 tokens

test-pyramid

Decide what type of test to write, structure the suite, measure health, and apply test doubles correctly.

sawrus/agent-guides · 26 tokens

fortify

Fortify existing code by splitting large functions, adding edge-case coverage, and backfilling unit tests. Use when user asks to "fortify", "harden", "bulletproof", "make robust", "make solid", "strengthen", "add missing tests", "split functions", or wants to improve reliability of existing code. Don't use for new…

helderberto/agent-skills · 93 tokens

testing-patterns

When writing tests for components, hooks, or integration flows.

sawrus/agent-guides · 0 tokens