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.
git 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/commands/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis)<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/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/commands/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis.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.00027 | $0.00799 |
| Opus 5 | $0.00014 | $0.00400 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
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 6d 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.
Read-only audit — produces coverage_analysis_report.md, does NOT create or modify Zephyr test cases
// turbo-all
1. Gather Input
If the Jira Issue Key is not provided, ask for it.
Optional: Scope (single ticket default, or comma-separated epic/sprint keys) | Depth (quick = coverage table only, full = default with risk scoring + QE observations).
2. Fetch Jira + Discover Zephyr TCs (Parallel Sub-Agents)
Launch two sub-agents in parallel to keep raw API data out of main context:
Sub-Agent A: Jira Analyst
Use
Agenttool withsubagent_type="jira-analyst". Prompt: "Fetch JIRA ticket {ISSUE_KEY} with?expand=renderedFields. Extract: Summary, Status, Components, Labels, Market, and the full AC table. For each AC row, read the Platform column from rendered HTML — color codes are authoritative:#00B8D9= Web,#36B37E= Mobile,#FF991F= Web+Mobile. Do NOT use ticket-level Platform — always read per-row from renderedFields. Return structured briefing."
Sub-Agent B: Zephyr Scanner
Use
Agenttool withsubagent_type="zephyr-scanner". Prompt: "Find all Zephyr test cases related to {ISSUE_KEY}. Use direct issue link lookup first, then supplemental search only if needed. Return the filtered TC table with key, name, platform, labels, objective summary."
Both agents run concurrently. Wait for both to complete before proceeding.
Merge Results
From Sub-Agent A: extract ACs with platform tags. From Sub-Agent B: extract the discovered TC list.
3. Map ACs to Coverage Status
Per platform slot (Web and Mobile are independent — Mobile covered ≠ Web covered):
| Status | Criteria |
|---|---|
| Covered | TC directly references this AC (label, objective, or step) and scope matches (platform, role, market) |
| Partial | TC exists but has generic objective, wrong role scope, different platform, or missing key assertions |
| Not Covered | No TC found |
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.
- 6d ago First seen · 68 lines · 27 tokens per session scan A 11d7f325ea7f
zephyr-coverage-analysis is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 799 once invoked, about $0.0001 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-06.
Other commands, from other repositories
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
e2e
An end-to-end testing assistant for guiding tests that exercise a complete user flow across an application. E2E tests check the system as a user would use it, rather than checking one small part in isolation.
journey-test
The /journey-test command turns a project description into a coherent user journey test plan (TESTPLAN-NNN.md) plus matching E2E skeletons, so a new project has a complete, ordered test journey from day one.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.