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-test-executionnpx skills add telus-labs/stagecraft --skill qa-test-executiongit 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-execution)<a href="https://agentmods.dev/skills/telus-labs/stagecraft/qa-test-execution"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/qa-test-execution.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.00056 | $0.01285 |
| Opus 5 | $0.00028 | $0.00642 |
| Sonnet 5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
qa-test-execution 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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Test-Execution Task (Stage 6 run phase)
Use this skill when you are the QA Developer running the test suite during
the Stage 6 execution phase. Test authoring is a separate step; see
skills/qa-test-authoring/SKILL.md.
Procedure
-
Run the full test suite via the project's standard command (
npm test,pytest, etc.). -
Produce
pipeline/test-report.mdwith this shape:# Test Report — <feature> **Run**: <ISO timestamp> **Total**: <n> tests — <p> passed / <f> failed ## Acceptance Criteria Coverage | # | Criterion | Test(s) | Result | |---|-----------|---------|--------| | 1 | <text> | `unit/ac1.test.ts::happy-path` | PASS | | 2 | <text> | `integration/ac2.test.ts` | FAIL | ## Failing Tests ### `integration/ac2.test.ts::…` -
Write
pipeline/gates/stage-06.json. Required fields:{ "stage": "stage-06", "status": "PASS" | "FAIL" | "ESCALATE", "workstream": "qa", "track": "<track>", "timestamp": "<ISO>", "all_acceptance_criteria_met": true | false, "tests_total": 0, "tests_passed": 0, "tests_failed": 0, "failing_tests": [], "assigned_retry_to": null, "affected_workstreams": [], "criterion_to_test_mapping_is_one_to_one": true | false }Set
criterion_to_test_mapping_is_one_to_onetotrueonly if every acceptance criterion has a dedicated test and no test covers multiple criteria with distinct verify conditions. When in doubt, setfalse.noted_for_followup[](non-blocking observations). When you observe something worth tracking that isn't a test failure — a coverage gap, a testability concern, a missing edge-case scenario the brief didn't require — emit it innoted_for_followupas a structured object rather than awarnings[]string. Usewarnings[]for transient issues (e.g. test suite configuration problems); usenoted_for_followupfor durable work items that should survive the pipeline run. Schema andtrack_forvalues are in.devteam/rules/gates-core.md §noted_for_followup[].
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.
- 4d ago First seen · 133 lines · 56 tokens per session scan A a0e6d532804d
qa-test-execution is a skill published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,285 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
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…