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-test-generationgit 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-test-generation)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation/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-test-generation"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation.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.00063 | $0.01245 |
| Opus 5 | $0.00032 | $0.00622 |
| Sonnet 5 | $0.00013 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
quality-engineering-zephyr-test-generation 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 13d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Test Generation Standards
Priority: P1 (HIGH)
Workflow: Jira → Zephyr
- Analyze Requirements:
- Extract: Summary, ACs, Platform per AC row, Market, Components.
- Fetch Jira with
?expand=renderedFields— HTML authoritative for platform colors:#00B8D9= Web ·#36B37E= Mobile ·#FF991F= Web+Mobile - See Actor/Permission Matrix for role/market logic.
- Impact Analysis (run before any TC creation)
- Step — Direct Lookup: Call
Get Issue Link Test Caseswith Jira issue key (e.g.,{PROJECT}-{ID}). - Step B — Supplemental: If Step 0, search by
[Module]and[Screen]keywords + check sibling issue links. - See Discovery Protocol for full chain.
- Map each AC to coverage status:
- Covered → ask user: skip or update to current format?
- Partial → always propose NEW TC.
- Not Covered → always create NEW TC.
- Draft Artifact:
- Delete any existing
zephyr_test_plan.mdbefore writing. - Follow 4-section format in TC Format Reference exactly.
- After writing: read back file and print full content in chat so user can review without opening it.
- Ask for: review approval, handling of Covered ACs, and Zephyr Folder ID.
- Create in Zephyr (after explicit user approval)
Create Test Case(withcustomFieldsincluded — no separate Update needed) →Create Test Case Steps→Create Test Case Issue Link- For updates to existing TCs: fetch current steps via
Get Test Case Steps, show before/after diff, wait for explicit approval, thenUpdate Test Case.
Platform Rules
| AC row | Action |
|---|---|
Single row [ WEB + MOBILE ] |
ONE TC, Platform = "Web and Mobile", no platform prefix in name |
| Two rows same behavior, different platforms | TWO TCs with Web_ / Mobile_ prefix — never merge |
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.
- 13d ago First seen · 95 lines · 63 tokens per session scan A 0782f11ddc07
quality-engineering-zephyr-test-generation is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 1,245 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
testing
Skill "testing" from udecode/plate-playground-template, covering testing goal, core rules, seam selection, fixtures and assertions and quick reference.
playtest
Drive a real browser against a game with vg playtest: smoke checks, scripted bot playtests, softlock detection, screenshots and visual diffs, on localhost or a deployed URL.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.