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-tasksgit 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-tasks)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/jira-tasks"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/jira-tasks/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-tasks"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/jira-tasks.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.00789 |
| Opus 5.5 | $0.00020 | $0.00316 |
| Sonnet 5.5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
jira-tasks 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Read Jira to answer "what am I working on", "what's the status of <PROJECT-KEY>-115", or to reconcile workspace tasks against tickets. Read-only by default — every write is a separate, explicit, user-requested action. <jira-base-url> and <PROJECT-KEY> come from the project's CLAUDE.md or .claude/project.json; if undocumented, ask once.
Rules
- Every write (create / transition / comment / worklog) requires an explicit user request in the current conversation — a request to list or check tickets never authorises a mutation. Sole exception:
jira-pack's/jira-fixruns carry their own write mandate. - Resolve Atlassian MCP tools by tool name via ToolSearch, never by a hardcoded channel prefix — two channels can expose the same tools under different prefixes.
- Every Jira call needs a cloudId from
getAccessibleAtlassianResources; on any 404, re-resolve rather than retrying a stale pinned id. - Render compact tables (key, status, summary, updated), most-recently-updated first — never dump raw issue JSON.
- The
Tickets:line in a workspace task-card README is the join key both directions; adding it is a workspace edit, never a Jira write.
Resources
- Read
resources/tool-flow-and-jql.mdwhen making any Jira call — deferred-tool loading, cloudId resolution, read-tool signatures, JQL recipes, output shape. - Read
resources/write-policy-and-task-links.mdwhen a write is requested or when linking tickets to workspace task cards — the full write-op policy, the/jira-fixexception, theTickets:convention, related skills.
How to use
What it does
Answers Jira questions without changing anything: your open tickets, one ticket's live status, what moved this week — returned as a compact table instead of raw JSON. It also links tickets to workspace task cards in both directions, so a lookup surfaces prior work already on disk.
When to use it
- You want your open tickets, a team's in-progress list, or a backlog view.
- You need the live status, assignee, and labels of one ticket by key.
- You want a task card's
Tickets:line reconciled against real Jira status. - Not for writes (each needs an explicit request), full autonomous runs (
/jira-fix), or Confluence.
What ships with it
2 files 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.
- 1mo ago First seen · 58 lines · 50 tokens per session scan A f67e780322fb
jira-tasks is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 789 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-09-03.
Other skills, from other repositories
execute
Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.
recipe-batch-invite-to-event
Add a list of attendees to an existing Google Calendar event and send notifications.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.
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.
recipe-organize-drive-folder
Create a Google Drive folder structure and move files into the right locations.