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 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/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/yarlson/yarstack/jira-issue-create"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/jira-issue-create.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.00053 | $0.01122 |
| Opus 5.5 | $0.00021 | $0.00449 |
| Sonnet 5.5 | $0.00011 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
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 — 100 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
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.
- 3d ago Changed · +1 lines c619d172d148
- 1mo 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 2d ago), licensed MIT. It adds 53 tokens to every session and 1,122 once invoked, about $0.0002 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-31.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…