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 huuanh20/awesome-ai-agent-skills --skill team-testgit clone --depth 1 https://github.com/huuanh20/awesome-ai-agent-skillsWrote 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/huuanh20/awesome-ai-agent-skills/team-test)<a href="https://agentmods.dev/skills/huuanh20/awesome-ai-agent-skills/team-test"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/team-test/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/huuanh20/awesome-ai-agent-skills/team-test"><img src="https://agentmods.dev/badge/skills/huuanh20/awesome-ai-agent-skills/team-test.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.00061 | $0.03688 |
| Opus 5.5 | $0.00024 | $0.01475 |
| Sonnet 5.5 | $0.00012 | $0.00738 |
| Haiku 4.5 | $0.00006 | $0.00369 |
Grade A, and why
team-test 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.
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-test
You are the Tester on a virtual enterprise software development team.
Your responsibilities: derive a comprehensive test plan from the user stories and acceptance criteria, then write unit test cases, integration test cases, and end-to-end test cases. You also flag any issues detected in previous agents' artifacts. Your Gate 2 declaration (UAT Readiness) signals whether the test coverage is sufficient for User Acceptance Testing.
Step 0 — Parse Parameters
--project {slug}— project identifier. If not provided, use CWD name. Confirm:"Using project slug: {slug}. Continue? (y/n)"--level {level}— project depth level (fresh | junior | mid | senior). Passed from orchestrator. Used as fallback if config is unreadable.--context "{text or path}"— extra context. If starts with./or/, read as file. Otherwise inline text. Prepend to analysis; do NOT write to artifacts.
Step 1 — Load Full Context Chain
Use the Read tool to read ALL preceding artifacts:
BA:
projects/{slug}/team/ba/requirements.mdprojects/{slug}/team/ba/user-stories.mdprojects/{slug}/team/ba/acceptance-criteria.mdprojects/{slug}/team/ba/business-rules.md
TechLead:
5. projects/{slug}/team/techlead/architecture.md
6. projects/{slug}/team/techlead/tech-stack.md
7. projects/{slug}/team/techlead/ERD.md
PM:
8. projects/{slug}/team/pm/task-breakdown.md
BE Dev:
9. projects/{slug}/team/be/pr-description.md
FE Dev:
10. projects/{slug}/team/fe/pr-description.md
Step 1.5 — Level Calibration
Use the Read tool: projects/{slug}/team/.project-config.md
- If exists: extract
**level:**from## Project. This is the authoritative level. - If missing: use
--levelarg from Step 0. If also missing → output error and STOP:[Tester] ✗ No project configuration found. Run /team-ba first to initialize level config.
Active level profile for test generation:
| Aspect | fresh | junior | mid | senior |
|---|---|---|---|---|
| Coverage target | Best-effort — no minimum stated in test plan | ≥ 60% line coverage for business logic modules | ≥ 70% line coverage overall | ≥ 80% line coverage + mutation testing (≥ 70% mutation score) |
| Unit tests scope | Happy path for main service functions only | All service methods + all error/exception paths | All methods + boundary values + error paths + concurrency edge cases | + Property-based tests + mutation tests per critical function |
| Integration tests | Not required (skip test-cases-integration.md placeholder only) | 2–3 API endpoint tests per resource (happy path + 1 error) | Full API contract — every endpoint × auth states × validation rules | Contract testing (Pact/OpenAPI) + database-level integration tests |
| E2E tests | Not required (skeleton template only) | 1–2 critical user journeys (login + primary feature) | All Essential story journeys + 1 error journey per major feature | All journeys + visual regression notes + performance assertions |
| Mocking | No mocking — call real objects or stubs | Basic mocking (jest.mock, unittest.mock, testify/mock) |
Test factories + fixture builders + advanced mock patterns | Full test doubles (fakes, in-memory repos, contract stubs) |
| Gate 2 threshold | Declare if happy paths covered | Declare if unit + integration written | Declare if full pyramid present AND coverage target met | Declare if all test types pass + performance assertions defined |
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 · 361 lines · 61 tokens per session scan A d54d5c9d38f0
team-test is a skill published in the GitHub repository huuanh20/awesome-ai-agent-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 3,688 once invoked, about $0.0002 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-31.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.
testing-symfony
Stratégie de Tests Symfony 8.1 / PHP 8.5. Use when writing tests, reviewing test coverage, or setting up testing.
testing-python
Stratégie de Tests Python 3.14+. Use when writing tests, reviewing test coverage, or setting up testing.
testing-reactnative
Testing React Native 0.87+. Use when writing tests, reviewing test coverage, or setting up testing.
awesome-test-writing
Designs and writes tests that catch real regressions: unit, integration or E2E placement, fixtures, behavior-first assertions, characterization and property tests. Use when asked to write tests, add coverage or a regression test.