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-delivergit 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-deliver)<a href="https://agentmods.dev/skills/yarlson/yarstack/jira-issue-deliver"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/jira-issue-deliver/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-deliver"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/jira-issue-deliver.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.00051 | $0.01928 |
| Opus 5.5 | $0.00020 | $0.00771 |
| Sonnet 5.5 | $0.00010 | $0.00386 |
| Haiku 4.5 | $0.00005 | $0.00193 |
Grade A, and why
jira-issue-deliver 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 6d 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 Delivery
Own one Jira issue from first read to a ready, green, reviewed pull request. Use the issue as the behavior contract, the repository as the implementation authority, and fresh evidence from the current remote PR head for completion.
Establish authority and completion
Confirm the Jira key or URL, repository, base branch, requested review systems, and terminal condition. Proceed only when the request authorizes edits, commits, pushes, PR creation and ready-state changes, CI fixes, review replies, and thread resolution. Read applicable repository instructions before any mutation.
This skill never merges, deploys, releases, or transitions Jira. Jira remains read-only unless the user separately authorizes a Jira mutation.
Finish only when current evidence proves that:
- one PR implements every in-scope acceptance criterion;
code-reviewran on the final complete diff, and each verified finding is fixed or recorded with a reason;- the PR is open and ready for review, not a draft;
- the remote PR head matches the validated commit;
- every required check for that head passed or has a neutral result allowed by repository rules;
- each requested automated reviewer completed its review of that head;
- each requested automated review thread has a recorded outcome supported by repository evidence, and each actionable thread is resolved;
- the PR title and body match the final diff and test evidence.
Maintain autonomous progress
Resolve questions from Jira, repository evidence, installed tool help, authorized integrations, and official public documentation before asking the user. Never send private issue or repository data to public search.
When several valid approaches remain, choose the smallest reversible one that preserves current behavior and scope, record the assumption, and continue. Ask one concise question only when missing authority or credentials, conflicting requirements, materially different behavior, or an irreversible or high-risk choice blocks progress. Do not treat silence as authority.
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.
- 6d ago Changed · +1 lines eeb4e61eb4d8
- 7d ago Changed · +1 lines 67df900c4ce0
- 1mo ago Changed · -77 lines 11229dc76dc1
- 1mo ago Changed 11d7808fd273
- 1mo ago First seen · 175 lines · 51 tokens per session scan A 19eb7ab59c88
jira-issue-deliver is a skill published in the GitHub repository yarlson/yarstack (3 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 1,928 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
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
finishing-a-development-branch
Open a PR or finish branch disposition; route CI watching and post-merge cleanup to their owners. Merge and discard need explicit authority.
ziw-implement
Use for implementation when taking one tracker issue through the full implementation pipeline by claiming the issue, making scoped changes locally or remotely, verifying, using judgment about author QA, running ziw-pr, and handing off for independent review.
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.
owndiff-pre-commit
Audit OwnDiff changes before committing or releasing by checking scope, generated artifacts, private data, documentation accuracy, version consistency, structured files, tests, and the OwnDiff ownership gate. Use when a user asks to verify, clean up, prepare, commit, publish, or release changes in the OwnDiff…
git-review
Review a repository diff for accidental changes, secrets, generated files, dependency and migration impact, tests, documentation, and scope before completion.