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 HoangNguyen0403/agent-skills-standard --skill quality-engineering-automation-healthgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/quality-engineering-automation-health)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-automation-health"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-automation-health/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/hoangnguyen0403/agent-skills-standard/quality-engineering-automation-health"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-automation-health.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.00059 | $0.00743 |
| Opus 5.5 | $0.00024 | $0.00297 |
| Sonnet 5.5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
quality-engineering-automation-health 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Engineering: Automation Health
Priority: P1 (HIGH)
Mission
Automation exists to reduce ambiguity at release time, not to catch every bug. Finding bugs is testing's job; building confidence is automation's. Judge a suite by whether the team can deploy on Friday afternoon without fear.
Three Questions
A high-value suite answers all three with evidence:
- Core workflows intact: the flows that create revenue and user value still run end to end.
- No serious regression: the latest change did not break what was already stable.
- Fast feedback: a developer learns what they broke in minutes, not hours.
Four Metrics
| Metric | Key | Question it answers |
|---|---|---|
| Feedback loop | feedback_loop_minutes |
How long from push to a trusted green or red? |
| Suite reliability | suite_reliability_pct |
When a run is red, does the team investigate or just re-run? |
| Release cadence | release_cadence |
Did automation let the team ship more often without more production risk? |
| Production escape rate | prod_escape_rate |
How many serious defects passed the whole pipeline and reached real users? |
Formulas and data sources per CI provider live in Metrics Definitions.
Verdict
release_confidence: high | medium | low
high: all three questions answered yes with evidence; reliability at or above the team threshold; escape rate at or below baseline; feedback loop within target.medium: one question lacks evidence, or reliability or feedback loop misses target while escapes stay at baseline.low: any question answered no, a red run is not trusted, or escape rate rose after the last release.
Report with Confidence Report Template; feed release_confidence into test-loop, uat-signoff, and deploy-release handoffs.
Anti-Patterns
- No ranking by bug count: a suite that catches few bugs on CI usually means developers catch them locally first; that is success, not waste.
- No deleting never-failing tests: a test that never fails is a safety net, not dead weight. It is what lets engineers refactor, bump dependencies, and change config without silent breakage.
- No coverage % as the goal: coverage measures lines touched, not confidence earned.
- No pass rate as health: a 99% pass rate with untrusted reds is worse than 95% the team believes.
What ships with it
3 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.
- 1mo ago First seen · 68 lines · 59 tokens per session scan A 61f9a2c3b594
quality-engineering-automation-health is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 743 once invoked, about $0.0002 per session on Opus 5.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-14.
Other skills, from other repositories
browser-automation
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
vue-idioms
Vue 3 Composition API patterns: syntax, reactive state with Pinia stores, reusable composables, and Vitest component testing. Use when developing or refactoring Vue 3 frontend applications.
python-idioms
Modern Python (3.11+) idioms: type annotations, typing Protocols, Pydantic models, asyncio, pytest fixtures, and Ruff/Mypy strict compliance. Use when writing, refactoring, or reviewing Python applications, APIs, or scripts.
testability-patterns
Implementation examples for the three testability rules (I/O isolation, pure logic, dependency direction) across Go, TypeScript, Python, Rust, and Dart. Loaded by reference from architectural-pattern.md — not triggered by file patterns.
testing-strategy
Detailed testing reference material: test doubles strategy, integration test infrastructure (Testcontainers, Firebase emulator), naming conventions per language, test organization patterns. Load when writing tests or setting up test infrastructure. The core mandates (TDD, AAA, pyramid) are in the testing-strategy rule…
react-testing
React testing guidance using React Testing Library and modern patterns.