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 telus-labs/stagecraft --skill qa-test-authoringgit clone --depth 1 https://github.com/telus-labs/stagecraftWrote 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/telus-labs/stagecraft/qa-test-authoring)<a href="https://agentmods.dev/skills/telus-labs/stagecraft/qa-test-authoring"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/qa-test-authoring/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/telus-labs/stagecraft/qa-test-authoring"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/qa-test-authoring.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.00064 | $0.00538 |
| Opus 5 | $0.00032 | $0.00269 |
| Sonnet 5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
qa-test-authoring 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 9d 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
QA Test-Authoring Task (Stage 6 authoring phase)
Use this skill when you are the QA Developer writing tests during the Stage 6
authoring phase. This phase produces the test code; running the suite is a
separate execution phase (see skills/qa-test-execution/SKILL.md).
Procedure
- Read
pipeline/context.md— check forPM-ANSWER:items and## Brief Changesthat affect acceptance criteria. - Read
pipeline/brief.mdcarefully. For each acceptance criterion in §3, plan at least one test that exercises it. Map one-to-one where possible — §3.1 → test "…ac1…", §3.2 → test "…ac2…". This mapping enables the sign-off auto-fold. 2a. Ifpipeline/spec.featureexists (stage-03b ran), it is the canonical list of behaviours to test. EveryScenario:in the file must have at least one test mapped to it. The Scenario name +@AC-Ntag are how the test-report mapping table cross-references back to the brief. Rundevteam spec verifyafter writing test-report.md to catch drift between brief / spec / report. - Append an
## Assumptionsblock topipeline/context.mdfor non-obvious test choices (e.g. "assuming deterministic clock via clock-injection; otherwise flaky on CI"). Per coding-principles §1. - Write tests in
src/tests/organised by type:src/tests/unit/— isolated logicsrc/tests/integration/— service interactionssrc/tests/e2e/— at least one E2E per acceptance criterion
- Match existing test conventions. If a convention is missing, read the
code-conventions skill and note in
pipeline/pr-qa.mdunder## Conventions applied. - Do not mock away real business logic. Test real behaviour. If a test requires a mock (network, clock, random), justify it inline with a one-line comment.
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.
- 9d ago First seen · 39 lines · 64 tokens per session scan A c64d3a38e081
qa-test-authoring is a skill published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 538 once invoked, about $0.0003 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.
Other skills, from other repositories
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
verify
Run the HUMHUM quality gates that are actually touched by the current diff — frontend typecheck + vitest, and Rust fmt/clippy/test — mirroring CI. Use before marking work done, opening a PR, or when asked to "verify", "check", or "run the gates".
test-generation
Generate comprehensive tests for code including unit tests, integration tests, and edge case coverage. Analyzes code to identify testable units and generates tests matching the project's testing framework and conventions.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.