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-zephyr-coverage-analysisgit 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-zephyr-coverage-analysis)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-coverage-analysis"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-coverage-analysis/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-zephyr-coverage-analysis"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-coverage-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.00521 |
| Opus 5.5 | $0.00032 | $0.00208 |
| Sonnet 5.5 | $0.00016 | $0.00104 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
quality-engineering-zephyr-coverage-analysis 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.
What it actually says
Zephyr Coverage Analysis
Priority: P1 (HIGH)
Workflow
CRITICAL — Read and follow workflow file exactly. NOT implement from memory or from this description. Implementing inline bypasses
jira-analystandzephyr-scannersub-agents.
Read and execute .agents/workflows/zephyr-coverage-analysis.md.
Anti-Patterns
- No TC creation: Analysis read-only — call quality-engineering-zephyr-test-generation to create TCs.
- No pagination-first: Always use
Get Issue Link Test Cases(direct lookup) before falling back to pagination. - No ticket-level platform: Read Platform from each AC table row HTML, not ticket header section.
- No merged WEB+MOBILE slots: Treat each platform as independent coverage slot — Mobile covered ≠ Web covered.
- No skipping QE debt: Scan beyond AC rows — always include data correctness, negative flows, role differentiation, and regression risk in Section 4.
References
- Report Template — load when building coverage_analysis_report.md (Step 5 of workflow)
- Impact Analysis Protocol — TC discovery protocol
- Zephyr Test Generation — invoke after analysis to create missing TCs
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
-
HIGH
-
P1
-
QE Debt
-
coverage_analysis_report.md
-
covered
-
Additional task-grounded exact anchors: zephyr-test-generation
What ships with it
2 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 · 55 lines · 81 tokens per session scan A 537cab6ff13f
quality-engineering-zephyr-coverage-analysis is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 521 once invoked, about $0.0003 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-08-30.
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.
mobile-testing
Mobile E2E testing patterns — Flutter integrationtest, Patrol, Maestro, golden testing, device matrix, and test data management. Use when writing E2E tests for mobile applications.
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…