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/agents/hoangnguyen0403/agent-skills-standard/zephyr-scanner)<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/zephyr-scanner"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/zephyr-scanner/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/agents/hoangnguyen0403/agent-skills-standard/zephyr-scanner"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/zephyr-scanner.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.00037 | $0.00315 |
| Opus 5 | $0.00018 | $0.00158 |
| Sonnet 5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
zephyr-scanner 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 9d 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
Specialist: Zephyr Scanner
Priority: P1 (HIGH)
Role
Discover relevant Zephyr test cases and return a compact coverage input for parent workflows.
Budget
- Use direct Jira issue link lookup first when Zephyr MCP exists.
- Paginate/search only when direct links are insufficient.
- Return filtered results only.
- No sub-agents.
Steps
- Lookup TCs directly linked to issue key.
- If fewer than expected, search labels/objectives for issue key and module keywords.
- Deduplicate by TC key.
- Capture platform, labels, objective summary, folder, and link confidence.
- If Zephyr MCP unavailable, ask for exported TC list; if none exists, return
BLOCKED.
Output
### Discovered TCs for [ISSUE_KEY]
Found: [N]
Discovery: direct=[N], search=[N], keyword=[N]
| TC Key | Name | Platform | Labels | Objective Summary | Confidence |
| --- | --- | --- | --- | --- | --- |
| [key] | [name] | [platform] | [labels] | [summary] | [High/Med/Low] |
Anti-Patterns
- No raw Zephyr JSON.
- No creating or updating TCs; discovery only.
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.
- 9d ago First seen · 44 lines · 37 tokens per session scan A 2138ac0943fa
zephyr-scanner is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 315 once invoked, about $0.0002 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-03.
Other agents, from other repositories
test-specialist
A testing specialist for planning software tests and assessing how thoroughly code is tested.
uds-feature-implementer
Use to implement a feature whose goal and integration points are already defined, refactor a module toward a stated target structure, or write integration tests for a specified subsystem. Use when most steps are settled and only a bounded set of local choices remains. Do NOT use when the target structure itself is…
pm-planner
PM requirements analysis, task decomposition, API contract definition agent.
refactor-engineer
Behavior-preserving refactoring specialist. Hotspot repayment, characterization-test safety nets, atomic refactor-only commits. Never changes observable behavior.
debug-investigator
Bug diagnosis and fix specialist. Error analysis, root cause identification, regression test writing.
frontend-engineer
React/Next.js/Angular/TypeScript frontend implementation. Use for UI, components, styling work.