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 jamesyang124/agent-skills --skill sdd-qa-to-jiragit clone --depth 1 https://github.com/jamesyang124/agent-skillsWrote 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/jamesyang124/agent-skills/sdd-qa-to-jira)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/sdd-qa-to-jira"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/sdd-qa-to-jira/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/jamesyang124/agent-skills/sdd-qa-to-jira"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/sdd-qa-to-jira.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.00059 | $0.02544 |
| Opus 5 | $0.00030 | $0.01272 |
| Sonnet 5 | $0.00012 | $0.00509 |
| Haiku 4.5 | $0.00006 | $0.00254 |
Grade A, and why
sdd-qa-to-jira 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sdd-qa-to-ticket — 89% identical, 68 lines differ
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD QA to Jira
This skill bridges the Implement and QA phases of the spec-kit native SDD workflow. It reads all spec-kit artifacts in the feature folder, derives end-to-end BDD scenarios, presents them to the RD for review, then creates QA sub-tickets under the existing root Jira ticket — no new root ticket is created.
Key principle: Sub-tickets describe what to verify (Given/When/Then), not how. SDET owns the testing method, order, and approach entirely.
QA Ticket Template (MANDATORY)
All QA sub-tickets must follow the BDD template at:
references/qa-ticket-template.md (relative to this skill folder: .agent-settings/skills/sdd-qa-to-jira)
Prerequisites
IMPORTANT: This skill requires the Atlassian MCP Server to be installed and configured.
Before using this skill, ensure:
- ✅ Atlassian MCP server is installed (see
.agent-settings/mcps/install-atlassian-mcp.sh) - ✅ Credentials are configured in
.env.mcp-atlassian - ✅ A PR is open (this is the prerequisite that proves implementation is committed and reviewable)
- ✅ The existing root Jira ticket key from Phase 7 is available (e.g.
PROJ-101) - ✅ The following MCP tools are available:
mcp__atlassian__jira_get_issuemcp__atlassian__jira_create_issuemcp__atlassian__jira_add_comment
If the MCP server is not configured, guide the user to run:
.agent-settings/mcps/install-atlassian-mcp.sh
Input Sources (Tiered by Priority)
| Priority | Source | Contribution |
|---|---|---|
| Core | prd-source.md |
Business intent and user-facing requirements → business-perspective BDD scenarios |
| Core | spec.md |
RD's technical interpretation → scenario context and constraints |
| Core | requirements.md |
Technical acceptance criteria → primary BDD scenarios |
| Core | plan.md |
Technical decisions, alternatives rejected → edge cases |
| Extended | Any other *.md in the feature folder |
ADRs, impl notes, discovery notes → richer edge cases |
| Required | Root Jira ticket key (from Phase 7) | Parent for QA sub-tickets |
| Optional | Confluence design review page ID | Version stamp reference |
What ships with it
2 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.
- 11d ago First seen · 233 lines · 59 tokens per session scan A b813e409592a
sdd-qa-to-jira is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,544 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-31.
Other skills, from other repositories
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.