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 agentmods add skills/telus-labs/stagecraft/qa-augmentationnpx skills add telus-labs/stagecraft --skill qa-augmentationgit 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-augmentation)<a href="https://agentmods.dev/skills/telus-labs/stagecraft/qa-augmentation"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/qa-augmentation.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00794 |
| Opus 5 | $0.00023 | $0.00397 |
| Sonnet 5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
qa-augmentation 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Post-Red-Team Test Augmentation (Stage 4c-qa)
Use this skill when you are the QA Developer and this task fires after the
red-team gate turns WARN or PASS following one or more fix cycles —
i.e., must_address_before_peer_review[] had entries that the build team
addressed via --patch --from red-team. It does NOT fire on the initial
Stage 4 build (that's the Test-Authoring task; see skills/qa-test-authoring/SKILL.md).
Why this step exists
Each red-team patch is applied with --skip-completed, leaving the Stage 4
QA gate unchanged. No regression test is written for the fix. Peer reviewers
must then verify the fix purely by static inspection, and the same bug class
can resurface in later builds or red-team cycles. A targeted test addition
closes both gaps before Stage 5 begins.
Procedure
-
Collect the full set of items that were addressed across all red-team cycles. Two sources:
pipeline/red-team-report.md— the narrative describing what changedpipeline/context.md— any## ⚠️ PATCH MODEsections injected by the orchestrator during the fix cycles; each names the items addressed
-
For each addressed item, read the patched file at the cited location and write a regression test that would fail if the original bug were reintroduced:
- Place regression tests in
src/tests/regression/(separate from the AC-mapped tests insrc/tests/unit/andsrc/tests/integration/). - Tag the test with a comment citing the red-team ID:
// regression: RT-01 - One test per item is the floor; add more if the item has multiple failure modes.
- Use the same mock/stub patterns already established in the test suite. Don't introduce new test infrastructure for augmentation.
- Place regression tests in
-
Run the full test suite:
npm test # or project equivalentAll tests — original AC suite plus augmentation — must pass. If a regression test fails against the current code, the red-team fix was incomplete; treat as a Case 2 (QA-within-build FAIL, see
docs/runbooks/fix-and-retry.md) for the affected workstream and do not advance to Stage 5 until resolved.
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.
- 5d ago First seen · 69 lines · 46 tokens per session scan A c6e3eaa07da9
qa-augmentation is a skill published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 794 once invoked, about $0.0002 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
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
semantix-guide
Troubleshoot and configure Semantix capabilities: Skills (project/custom/global/builtin priority, discovery dirs), Commands (override order, /dir:file naming), Hooks (11 events, automatic project loading, matchers, timeouts), MCP (semantix-agent.toml + .mcp.json + plugin packages, autostart), plugin packages…
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…
intuitive-flow
Stable execution/change router after an approved plan, preflight contract, or tiny concrete task. Refactor-shaped work delegates to intuitive-refactor, and durable work runs through staged planning, review, GSD handoff, implementation, cleanup, and verification while keeping plan ledgers and active capsules compact by…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…