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 agentmods add skills/yarlson/yarstack/jira-issue-createnpx skills add yarlson/yarstack --skill jira-issue-creategit clone --depth 1 https://github.com/yarlson/yarstackWrote 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/yarlson/yarstack/jira-issue-create)<a href="https://agentmods.dev/skills/yarlson/yarstack/jira-issue-create"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/jira-issue-create.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.01037 |
| Opus 5 | $0.00026 | $0.00518 |
| Sonnet 5 | $0.00011 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
jira-issue-create 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Issue Creation
Create one Jira issue or a batch of issues with three plain ADF sections: Context, Acceptance criteria, and Engineering notes. Render each section title as a heading and do not wrap sections in panels.
Inputs
Extract these values from the request:
project(required): Jira project key, such asDXAI. Ask if missing.parent(optional): Epic or parent key for the created issues.type(optional): Work item type. Default toTask.content source(optional): Local document, pasted text, or prose describing the issue or issues. For a batch, identify what defines one issue.
Workflow
1. Check authentication
Run acli auth status. If authentication is missing, stop and ask the user to run acli auth login. Suggest ! acli auth login when an interactive command is needed.
Continue only when the output shows ✓ Authenticated for the expected site.
2. Gather content
- Read any referenced source document.
- When a parent is given, fetch it for context and tone with
acli jira workitem view <EPIC> --json. - Draft these sections for each issue:
- Context: Explain why the issue exists, what it covers, and its role in the larger effort.
- Acceptance criteria: Use an ordered list. Start each item with a bold lead phrase followed by one sentence, such as "Pilot flows run: ...".
- Engineering notes: Use bullets with bold labels for risks, constraints, useful details, and relevant links.
Gloss bare identifiers such as KR2, G4, or U3 with a short inline explanation. Use only requirements from the request or source material. Do not invent requirements.
3. Confirm drafts
This is a human checkpoint. Do not call any tool in this step because a dialog can hide the draft that the user must review.
Send one Markdown message with:
- Each issue summary as a heading.
- The complete Context, Acceptance criteria, and Engineering notes content that will be created.
- This final line: "Reply approve to create the issue(s), or tell me what to change."
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.
- 3d ago First seen · 99 lines · 53 tokens per session scan A 0464118bb2da
jira-issue-create is a skill published in the GitHub repository yarlson/yarstack (3 stars, last pushed 6d ago), licensed MIT. It adds 53 tokens to every session and 1,037 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
repository-bootstrap
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.
linear
Use Symphony's generated typed Linear tools for tracker workflow actions. Provides Linear capability semantics and workpad rules.
tapd
Use Symphony's generated typed TAPD tools for tracker workflow actions. Provides TAPD capability semantics and workpad rules.
k-onboard
为仓库建立首份经过核实的项目地图和 Agent 协作契约。.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.