Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add atretyak1985/swarmery/plugin install jira-packWrote 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-escalation)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/jira-escalation"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/jira-escalation/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-escalation"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/jira-escalation.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.00112 | $0.03745 |
| Opus 5 | $0.00056 | $0.01872 |
| Sonnet 5 | $0.00022 | $0.00749 |
| Haiku 4.5 | $0.00011 | $0.00375 |
Grade A, and why
jira-escalation 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Make "this is bigger than an autonomous /jira-fix run" a soft landing
instead of a dead end. When a ticket or a fix attempt outgrows
jira.budget, the work already done (evidence, diagnosis, partial fix
attempts) is not thrown away — it becomes a phased plan, saved where every
other plan in this project lives, with its full text posted back to the
ticket so a human can pick it up without needing local filesystem access.
When to use
Called from two places:
jira-triage, before any repro attempt, when a ticket is self-evidently an epic or multi-stage feature (its own early-exit note). No branch exists yet in this path.jira-delivery, mid-attempt, once one of the budget/verification triggers below fires. A branch and worktree may already exist in this path and must be cleaned up (Step 4).
Triggers (any one of these five fires escalation)
jira.budget.maxFilesexceeded — the executor's diff touches more files than the budget allows, independent of whether verification passed (jira-delivery's own second gate).jira.budget.maxAttemptsexceeded — that many delegate→verify cycles have run without a qualifyingPASS.@debuggerreturned an escalation under its own stop conditions (fix spiral, 3 failed attempts, ~5 files —plugins/core/agents/debugger.md) beforejira.budget.maxAttemptswas independently exhausted; treat this the same as trigger 2 rather than waiting for the outer counter to also run out.@verification-agentreturnedFAILandjira.budget.maxAttemptsis already exhausted (aFAILwith attempts remaining is not itself a trigger —jira-deliveryre-dispatches instead).jira-triageclassified the tickettoo-largeat triage time, before any reproduction attempt.
Step 1 — brief the planner
@planner (plugins/core/agents/planner.md) handles both scopes: a
single defect or small feature that simply exceeded the autonomous budget
gets a compact 3-5 phase plan, while a genuinely multi-phase ticket (an
epic, a cross-repo migration) gets a full multi-phase plan. State the scope
signal in the brief — triage's too-large reason, roughly how long the work
looks — so the planner sizes the plan deliberately.
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 · 281 lines · 112 tokens per session scan A aa8c68ff13d3
jira-escalation is a skill published in the GitHub repository atretyak1985/swarmery (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 112 tokens to every session and 3,745 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
execute
Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.
recipe-post-mortem-setup
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
recipe-batch-invite-to-event
Add a list of attendees to an existing Google Calendar event and send notifications.
recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
recipe-find-free-time
Query Google Calendar free/busy status for multiple users to find a meeting slot.