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.
git 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/commands/atretyak1985/swarmery/jira-fix)<a href="https://agentmods.dev/commands/atretyak1985/swarmery/jira-fix"><img src="https://agentmods.dev/badge/commands/atretyak1985/swarmery/jira-fix/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/commands/atretyak1985/swarmery/jira-fix"><img src="https://agentmods.dev/badge/commands/atretyak1985/swarmery/jira-fix.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.00050 | $0.01858 |
| Opus 5 | $0.00025 | $0.00929 |
| Sonnet 5 | $0.00010 | $0.00372 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
jira-fix 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 7d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/jira-fix — drive a tracker ticket end-to-end
Usage
/jira-fix <url|KEY> [--dry-run] [--repo <path>]
Examples:
/jira-fix <PROJECT-KEY>-123/jira-fix https://<jira-base-url>/browse/<PROJECT-KEY>-123 --dry-run/jira-fix <PROJECT-KEY>-123 --repo ../other-checkout
This command is invoked the same way from an interactive session and from the
ai-prompt step of a scheduled routine (tools/swarmery/internal/routines/doc.go:3
— the prompt arrives on the headless session's stdin), which is why a stable
command entry point exists at all rather than only an agent that has to be
addressed by name.
What it does — and does not do
This is a thin proxy. It parses $ARGUMENTS, validates the shape of the
ticket reference and the flags, and delegates everything else — config
resolution, access preflight, the board card, triage, writeback — to
@jira-task-runner (plugins/jira-pack/agents/jira-task-runner.md). No run
logic is duplicated here. That includes the ticket's class (defect vs
change): this command never inspects the ticket, so it cannot know which one
it is, and the flags it forwards are identical either way.
In particular, this command does not:
- check that a
--repopath exists or is a git repository — that isjira-config's job, inside the agent it hands off to; - validate
.claude/project.json'sjirablock — same skill, same reason; - resolve Jira access, read the ticket, run a reproduction, classify, comment,
or transition — all of that is
@jira-task-runner's job downstream.
If argument parsing fails, stop and report a usage error. Do not invoke the
agent on an unparseable reference — an agent run that immediately fails inside
jira-config/jira-access-preflight on a malformed key is a wasted turn this
command's own regex check exists to avoid.
Argument parsing
- Ticket reference (first positional argument) — exactly one of:
- a bare key:
<PROJECT-KEY>-<number>, e.g.ABC-123, matching^[A-Z][A-Z0-9]*-[0-9]+$; - a browse URL:
https://<jira-base-url>/browse/<KEY>— extract<KEY>from the path segment following/browse/and validate that extracted key against the same regex.
- a bare key:
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.
- 7d ago First seen · 151 lines · 50 tokens per session scan A 3e4990633304
jira-fix is a command published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,858 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-09-03.
Other commands, from other repositories
gws-tasks
List, create, complete, and manage Google Tasks.
gws-standup
Generate a standup report combining today's calendar and tasks.
status
Display project status, active tracks, and next actions.
decision
Record, list, and manage project decisions with rationale tracking.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.