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 ulises-jeremias/agent-toolkit --skill jira-bulk-operationsgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/jira-bulk-operations)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/jira-bulk-operations"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/jira-bulk-operations/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/ulises-jeremias/agent-toolkit/jira-bulk-operations"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/jira-bulk-operations.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.00121 | $0.02311 |
| Opus 5 | $0.00060 | $0.01156 |
| Sonnet 5 | $0.00024 | $0.00462 |
| Haiku 4.5 | $0.00012 | $0.00231 |
Grade A, and why
jira-bulk-operations 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.
This is a copy
97% identical to jira-bulk-operations — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-bulk
Bulk operations for JIRA issue management at scale - transitions, assignments, priorities, cloning, and deletion.
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| Dry-run any operation | - |
Preview only, no changes |
| Bulk transition | !! |
Affects many issues; use --dry-run first |
| Bulk assign | !! |
Affects many issues; use --dry-run first |
| Bulk set-priority | !! |
Affects many issues; use --dry-run first |
| Bulk clone | ! |
Creates many issues; can delete |
| Bulk delete | !!! |
IRREVERSIBLE - issues permanently lost |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
CRITICAL: Always use --dry-run before executing bulk operations. Bulk delete is permanent and cannot be undone.
When to use this skill
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
Use this skill when you need to:
- Transition multiple issues through workflow states simultaneously
- Assign multiple issues to a user (or unassign)
- Set priority on multiple issues at once
- Clone issues with their subtasks and links
- Delete multiple issues permanently (with dry-run preview)
- Execute operations with dry-run preview before making changes
- Handle partial failures gracefully with progress tracking
Scale guidance:
- 5-10 issues: Preview (default behavior), then re-run with
--yes - 50-100 issues: Use
--dry-runfirst, then execute with--yes - 500+ issues: Use
--dry-run, then execute in smaller batches if needed
Quick Start
# Preview before making changes (bulk commands run as a preview by default)
jira-as bulk transition --jql "project=PROJ AND status=\"In Progress\"" --to Done --dry-run
# Execute the transition (--yes is required to apply changes)
jira-as bulk transition --jql "project=PROJ AND status=\"In Progress\"" --to Done --yes
For more patterns, see Quick Start Guide.
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 · 238 lines · 121 tokens per session scan A a720ff0e24cc
jira-bulk-operations is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (17 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 2,311 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to jira-bulk-operations, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
breaking-down-work
Decomposes a goal, feature, epic, or deliverable into a structured task tree (tasks, subtasks, checklists) with dependencies in Astravue. Use when the user wants to break down, decompose, or plan out work, turn an epic or feature into tasks, "split this into tasks", scope a deliverable, or build a work breakdown…
capturing-meeting-actions
Extracts action items from meeting notes, transcripts, or a brain dump and creates them as owned, dated tasks in Astravue. Use when the user pastes meeting notes or a transcript, asks to turn notes or standup discussion into tasks, capture action items, or "make tasks out of this".
mapping-dependencies
Maps task dependencies in an Astravue project, finds the critical path and blocked work, and detects circular dependencies before any rescheduling. Use when the user asks about dependencies, blockers, what's blocking what, the critical path, or wants to understand or fix the sequencing of a project.
triaging-overdue-work
Reviews overdue and at-risk tasks in Astravue, assesses why each is slipping, and proposes reschedule, reassign, deprioritize, or close actions before applying them. Use when the user asks what's overdue, behind schedule, slipping, or at risk, wants to catch up on a project, or clean up late work.