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 jaktestowac/awesome-copilot-for-testers --skill documenting-test-suitesgit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/documenting-test-suites)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/documenting-test-suites"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/documenting-test-suites/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/jaktestowac/awesome-copilot-for-testers/documenting-test-suites"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/documenting-test-suites.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.02070 |
| Opus 5 | $0.00042 | $0.01035 |
| Sonnet 5 | $0.00017 | $0.00414 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade A, and why
documenting-test-suites 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 10d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documenting Test Suites
Use this skill when a test suite is understandable only to the person who wrote it.
Test documentation has one job: get a competent stranger from a fresh clone to a passing local run, and then let them change something without breaking a convention they could not have known about. Everything that does not serve that is decoration.
The discipline that keeps it useful is knowing what not to write. A document that restates what the code already says goes stale within a sprint and then actively misleads. Document what the reader cannot find by looking: the unwritten convention, the reason behind a choice, the gotcha no config file confesses.
When to Use
- a new joiner needs to run the suite and there is no path from clone to green
- "how do I run just the API tests" is a recurring question
- a suite has been inherited and nobody knows why it is shaped the way it is
- a test architecture decision was made and will be re-argued in six months
- tags exist and their meanings live in one person's head
- fixtures and seed data have rules that only surface when you break them
Operating Principles
- Write what the environment cannot tell you. A list of npm scripts belongs in
package.json; the reason two of them exist belongs in the README. - Optimize for the first hour. The most valuable page gets a stranger to a green run. Everything else is secondary.
- Every command in the docs is copy-pasteable and has been run. An untested command is a broken promise with a trust cost.
- Decisions get a record, not a comment. Why page objects and not fixtures, why this runner, why the suite is split this way. Those get re-litigated without a record.
- Ownership is named. A suite with no owner has no maintainer, and the documentation is where that becomes visible.
- State what is not covered. A reader who assumes coverage that does not exist is worse off than one who knows the gap.
Workflow
Phase 0: Identify the readers
What ships with it
4 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.
- 10d ago First seen · 175 lines · 83 tokens per session scan A 8ea1d68f4f76
documenting-test-suites is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 14d ago), licensed MIT. It adds 83 tokens to every session and 2,070 once invoked, about $0.0004 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
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
crap-score
Calculates CRAP (Change Risk Anti-Patterns) for a named .NET method, class, or file. USE FOR: explicit CRAP calculation or coverage-and-complexity risk within that named target, including which tests to prioritize. DO NOT USE FOR: project-wide coverage/CRAP, plateaus, or project-wide blockers/priorities…
nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution. USE FOR: writing or reviewing NUnit tests; using [Test], [TestCase], [TestFixture], [SetUp], [TearDown] attributes; configuring…
michel-create-packmind-dataset
Seed a local Packmind instance with a realistic dataset — one organization populated with standards, commands, and skills — so an autonomous agent can exercise its own changes against lifelike data instead of an empty app. Use this whenever you need populated Packmind data to verify a change end-to-end: reproducing a…