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 naodeng/awesome-qa-skills --skill release-testing-workflowgit clone --depth 1 https://github.com/naodeng/awesome-qa-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/naodeng/awesome-qa-skills/release-testing-workflow)<a href="https://agentmods.dev/skills/naodeng/awesome-qa-skills/release-testing-workflow"><img src="https://agentmods.dev/badge/skills/naodeng/awesome-qa-skills/release-testing-workflow/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/naodeng/awesome-qa-skills/release-testing-workflow"><img src="https://agentmods.dev/badge/skills/naodeng/awesome-qa-skills/release-testing-workflow.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.00040 | $0.00475 |
| Opus 5 | $0.00020 | $0.00237 |
| Sonnet 5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
release-testing-workflow 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
31 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.
- agents/openai.yaml 476 B
- evals/cases/basic-success.yaml 718 B
- evals/cases/edge-gates-handoff.yaml 786 B
- evals/cases/edge-incomplete-input.yaml 733 B
- evals/eval.yaml 557 B
- output-templates/template-csv.csv 206 B
- output-templates/template-excel.tsv 358 B
- output-templates/template-json.json 393 B
- output-templates/template-markdown.md 250 B
- output-templates/template-word.md 302 B
- output-templates/template-xmind.md 317 B
- prompts/release-testing-workflow.md 4.8 KB
- README.md 863 B
- reference.md 954 B
- scripts/batch_convert_templates.py 2.7 KB runs code
- scripts/convert_formats.py 10 KB runs code
- scripts/convert_output_formats.py 255 B runs code
- scripts/convert_to_csv.py 270 B runs code
- scripts/convert_to_excel.py 272 B runs code
- scripts/convert_to_json.py 271 B runs code
- scripts/convert_to_markdown.py 275 B runs code
- scripts/convert_to_word.py 271 B runs code
- scripts/convert_to_xmind.py 272 B runs code
- scripts/parse_csv.py 272 B runs code
- scripts/parse_excel.py 274 B runs code
- scripts/parse_formats.py 5.9 KB runs code
- scripts/parse_json.py 273 B runs code
- scripts/parse_markdown.py 277 B runs code
- scripts/parse_output_formats.py 253 B runs code
- scripts/parse_word.py 273 B runs code
- scripts/parse_xmind.py 274 B runs code
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 · 50 lines · 40 tokens per session scan A 1ac3c79b0063
release-testing-workflow is a skill published in the GitHub repository naodeng/awesome-qa-skills (200 stars, last pushed 5d ago), with no licence file. It adds 40 tokens to every session and 475 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-09-03.
Other skills, from other repositories
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
shared-tooling-changesets
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation.
release-notes-generator
A writing tool that turns a plain-text sprint summary or product update into release notes for a changelog, email, in-app message, and social post.
verify-cli
Run smoke tests against the mpak CLI to verify all commands work correctly before publishing a new release.
release-checklist
Create go/no-go release checklists with pre-deploy verification, staged rollout steps, monitoring checkpoints, rollback triggers, and stakeholder communication plans.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.