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 atretyak1985/swarmery --skill jira-deliverygit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/jira-delivery)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/jira-delivery"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/jira-delivery/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/atretyak1985/swarmery/jira-delivery"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/jira-delivery.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.00114 | $0.06386 |
| Opus 5 | $0.00057 | $0.03193 |
| Sonnet 5 | $0.00023 | $0.01277 |
| Haiku 4.5 | $0.00011 | $0.00639 |
Grade A, and why
jira-delivery 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 8d 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Turn a needs-fix verdict into real, verified, published work without the
orchestrator (@jira-task-runner) ever editing code itself. This skill owns
exactly six things: the isolated branch, the red-test-first step on change
tickets, delegation to the right executor, the verification gate, the commit +
PR, and the writeback. Anything that outgrows jira.budget mid-flight is not
this skill's problem to solve — it hands off to jira-escalation (see
Related) and stops.
When to use
Called by @jira-task-runner's Fork (step 5), needs-fix row, strictly
after jira-triage has produced the evidence bundle for either class:
class: defect— reproduction command, exit code, output fragment, extracted repro steps, for a ticket whose reproduction ran red.class: change— the green baseline run, the absence proof (what was searched and what was found), and the numbered testable acceptance criteria. There is no red command yet: producing one is this skill's Step 2a, and it is a precondition for any implementation work.
Never invoked directly on a too-large verdict — that never reaches this
skill at all.
The class decides the shape of the run
class: defect |
class: change |
|
|---|---|---|
| Red evidence | Already in hand (jira-triage's failing reproduction) |
Produced here, in Step 2a, as a failing acceptance test |
| Branch | fix/<KEY>-<slug> |
feat/<KEY>-<slug> |
| Worktree dir | <worktree-root>/fix-<key>-<slug> |
<worktree-root>/feat-<key>-<slug> |
| Commit type | fix(<scope>): … [<KEY>] |
feat(<scope>): … [<KEY>] |
| Writeback template | comment-fix-summary.md |
comment-change-summary.md |
Everywhere below, <branch> and <worktree> mean whichever of the two rows
above the run's class selected. Nothing else in the flow differs: the same
verification gate, the same budget ceilings, the same escalation triggers, the
same comment-then-transition ordering.
Step 1 — branch, in an isolated git worktree
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.
- 8d ago First seen · 450 lines · 114 tokens per session scan A fe22b57c2414
jira-delivery is a skill published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 114 tokens to every session and 6,386 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
incremental-implementation
Use when implementing a multi-file change, building a feature from a breakdown, or writing a large amount of code. Not for a single settled ticket: use work.
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
claim
Acquire, renew or release a Fakoli State task lease when beginning work or recovering an interrupted claim.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.