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-jira-integrationgit 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-jira-integration)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-jira-integration"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-jira-integration/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-jira-integration"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-jira-integration.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.00075 | $0.00607 |
| Opus 5.5 | $0.00030 | $0.00243 |
| Sonnet 5.5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
quality-engineering-jira-integration 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
Jira Integration Standards
Priority: P1 (HIGH)
1. Retrieving Issue Details
- Fetch Core Info: Retrieve Summary, Description, Acceptance Criteria (AC), and Components.
- Jira Key: ALWAYS reference issue by its unique Jira Ticket ID (e.g.,
TICK-123). - Sibling Analysis: Identify other Jira issues with same Component or Market Variants (VN/MY/SG) to find potentially impacted Zephyr TCs.
- Identify Links: Use
Get Issue Link Test Caseswith Jira issue key to check for existing linked TCs before creating duplicates. - Actor Mapping: Extract reporter, assignee, and Story Points for context.
2. Linking Zephyr Test Cases
- Traceability: After creating Zephyr Test Case, link it back to corresponding Jira Issue using Remote Link or Zephyr Issue Link.
- Format: Use Zephyr Scale key (e.g.,
PROJ-T123) in Jira link or comment. - Labels: Apply
has-zephyr-testslabel to Jira issue once test cases successfully linked.
3. Jira-Zephyr Workflow
- Fetch: Get Jira User Story details.
- Generate: Create Zephyr Test Case using generation skill.
- Link: Use SmartBear MCP tool
Create Test Case Issue Linkto bridge two. - Notify: Add comment to Jira:
Linked Zephyr Test Case: {test_case_key}.
4. Best Practices
- Concise Summaries: Keep Jira comments professional and brief.
- Traceability Matrix: Ensure every AC in Jira at least one linked Zephyr Test Case.
- Cleanup: Remove unused labels or outdated links during refactors.
5. Anti-Patterns
- No Ghosting: Create tests then link to Jira (Traceability).
- No Spam: Post single comment per link.
- No Missing Labels: Update Jira labels after linking.
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- Identify
- has-zephyr-tests label
What ships with it
1 file 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 · 75 tokens per session scan A c720249e4dda
quality-engineering-jira-integration is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 607 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.
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…
react-testing
React testing guidance using React Testing Library and modern patterns.