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 sonature-lab/timsquad --skill tsq-testinggit clone --depth 1 https://github.com/sonature-lab/timsquadWrote 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/sonature-lab/timsquad/tsq-testing)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/tsq-testing"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sonature-lab/timsquad/tsq-testing"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/tsq-testing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00085 | $0.00630 |
| Opus 5.5 | $0.00034 | $0.00252 |
| Sonnet 5.5 | $0.00017 | $0.00126 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
tsq-testing 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 1mo 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.
What it actually says
Testing
품질 보장을 위한 테스트 작성 가이드라인.
Philosophy
- Red-Green-Refactor (TDD 사이클) 준수
- 테스트 피라미드: Unit(다수) > Integration(중간) > E2E(소수)
- 행동(behavior) 테스트 — 구현 디테일이 아닌 결과 검증
Contract
- Trigger: 테스트 작성/수정 태스크, 코드 변경 후 테스트 필요 시
- Input: 테스트 대상 코드 + 요구사항
- Output: Given-When-Then 패턴 테스트 + 커버리지 기준 충족
- Error: 커버리지 미달 시 추가 테스트 작성
- Dependencies: 없음
Protocol
- Red: 실패하는 테스트 작성
- Green: 테스트를 통과하는 최소 코드 작성
- Refactor: 코드 정리 (테스트는 계속 통과)
- Coverage 확인: 기준 충족 여부 점검
Verification
| Check | Command | Pass Criteria |
|---|---|---|
| 테스트 실행 | npm test |
exit code 0 |
| 라인 커버리지 | coverage report | >= 80% |
| 브랜치 커버리지 | coverage report | >= 70% |
| 3카테고리 | 수동 검증 | Happy/Edge/Error 포함 |
Resources
| Priority | Type | Resource | Description |
|---|---|---|---|
| HIGH | ref | testing-patterns | Given-When-Then, Mock 가이드 |
| HIGH | ref | e2e-stability | E2E Viewport, Wait, Retry 가이드 |
Quick Rules
Test Naming
- 형식:
should {expected behavior} when {condition} - Bad:
test getUser,works correctly
Test Categories
- Happy Path — 정상 흐름
- Edge Cases — 경계 조건 (빈 문자열, 0, null, 최대값)
- Error Cases — 오류 상황
Coverage Standards
| Metric | Min | Recommended |
|---|---|---|
| Line | 80% | 90% |
| Branch | 70% | 80% |
| Function | 80% | 90% |
What ships with it
2 files 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.
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.
- 1mo ago First seen · 70 lines · 85 tokens per session scan A 70b98751459b
tsq-testing is a skill published in the GitHub repository sonature-lab/timsquad (12 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 630 once invoked, about $0.0003 per session on Opus 5.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
nw-test-organization-conventions
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
automacao-de-testes
Automação de testes: unitários (Jest, Pytest), integração (supertest, httpx) e E2E com Playwright. Inclui estratégia de pirâmide de testes, cobertura mínima, CI/CD integration e testes para contexto brasileiro (CPF, CNPJ, CEP, PIX).
testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.
test-writing
Writes meaningful tests that actually catch bugs.
testing-strategy
Write comprehensive test suites with proper structure, mocking strategies, fixtures, and coverage goals. Use when implementing unit tests, integration tests, or e2e tests. Triggers on: tests, testing, unit test, integration test, e2e, jest, vitest, pytest, mocking, TDD.
test-generation
Generate a test strategy and starter test stubs for given modules across unit, integration, and e2e layers (pytest/jest/playwright). Trigger on: generate tests, test plan, test strategy, coverage plan, test scaffolding.