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 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/zephyr-coverage-analysis)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis"><img src="https://agentmods.dev/badge/skills/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/skills/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/zephyr-coverage-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 57 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 61 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00033 | $0.00928 |
| Opus 5.5 | $0.00013 | $0.00371 |
| Sonnet 5.5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
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 28d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Coverage Analysis Skill
[!IMPORTANT] Analyze Zephyr test case coverage for a Jira user story and produce a QE management report with metrics, risk scoring, and prioritized recommendations.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
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
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.
- 28d ago Changed · +1 lines a56744e1b25f
- 1mo ago First seen · 86 lines · 33 tokens per session scan A 39c027c40ee6
zephyr-coverage-analysis is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 928 once invoked, about $0.0001 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-03.
Other skills, from other repositories
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
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.
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.
test-e2e
Plans, authors, and executes end-to-end tests for mobile and web platforms. User-invoked entry point via /test-e2e; not for autonomous or subagent use.
test-integration
Audits I/O adapters, sets up test infrastructure, and systematically improves integration test coverage. User-invoked entry point via /test-integration; not for autonomous or subagent use.
testing-guide
A testing guide covering the test pyramid and standards for unit, integration, system, and end-to-end tests.