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 grandcamel/JIRA-Assistant-Skills --skill jira-agilegit clone --depth 1 https://github.com/grandcamel/JIRA-Assistant-SkillsWrote 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/grandcamel/jira-assistant-skills/jira-agile)<a href="https://agentmods.dev/skills/grandcamel/jira-assistant-skills/jira-agile"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-agile/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/grandcamel/jira-assistant-skills/jira-agile"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-agile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00145 | $0.02367 |
| Opus 5 | $0.00072 | $0.01184 |
| Sonnet 5 | $0.00029 | $0.00473 |
| Haiku 4.5 | $0.00015 | $0.00237 |
Grade A, and why
jira-agile-management 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- jira-agile-management — 95% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-agile
Agile and Scrum workflow management for JIRA - epics, sprints, backlogs, and story points.
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| List boards/sprints/epics | - |
Read-only |
| Get backlog/velocity | - |
Read-only |
| Create epic | - |
Easily reversible (can delete) |
| Create subtask | - |
Easily reversible (can delete) |
| Create sprint | - |
Easily reversible (can delete) |
| Add issues to epic | ! |
Can move to different epic or remove |
| Move issues to sprint | ! |
Can move back to backlog |
| Set story points | ! |
Can update estimate |
| Start sprint | ! |
Sprint state change |
| Close sprint | ! |
Cannot undo - issues move to next sprint |
| Rank issues | ! |
Can re-rank |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
When to use this skill
Use this skill when you need to:
- Discover boards and board IDs for a project
- Create and manage epics for organizing large features
- Link issues to epics for hierarchical planning
- Create subtasks under parent issues
- Track epic progress and story point completion
- Create and manage sprints on Scrum boards
- Move issues between sprints and backlog
- Prioritize and rank backlog issues
- Estimate issues with story points
- Calculate team velocity from completed sprints
Do not use this skill when:
- Creating individual stories/tasks without epic context (use jira-issue)
- Searching issues by JQL (use jira-search)
- Transitioning issues through workflow (use jira-lifecycle)
- Managing time tracking/worklogs (use jira-time)
- Discovering field configurations (use jira-fields)
See Skill Selection Guide for detailed guidance.
What this skill does
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
1. Epic Management
Create epics with Epic Name and Color fields, link stories/tasks to epics, and track epic progress with story point calculations.
What ships with it
12 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.
- docs/BEST_PRACTICES.md 35 KB
- docs/FIELD_REFERENCE.md 2.1 KB
- docs/OPTIONS.md 2.1 KB
- docs/QUICK_START.md 2.7 KB
- docs/SKILL_SELECTION.md 2.5 KB
- docs/TROUBLESHOOTING.md 3.0 KB
- docs/WORKFLOWS.md 3.6 KB
- examples/backlog-management.md 2.3 KB
- examples/epic-management.md 2.7 KB
- examples/estimation.md 2.9 KB
- examples/README.md 1.7 KB
- examples/sprint-lifecycle.md 3.4 KB
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.
- 12d ago First seen · 210 lines · 145 tokens per session scan A 7fef17d29a71
jira-agile-management is a skill published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 3d ago), licensed MIT. It adds 145 tokens to every session and 2,367 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
reality-strategy
Change a blocked real-life or organisational situation by recovering the original result, reconstructing real participants and flows, investigating the sustaining cause, mapping stakeholders and practical power, then altering defaults, burdens, incentives, coalitions, information flow, decision rights or action…
mk:jira
Routing skill — recommends the correct mk:jira- leaf for any Jira task. Triggers: 'jira', 'jira ticket', ambiguous Jira intent. NOT an executor — every actual operation forks via a leaf skill.
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
python-logging-best-practices
Python logging with loguru, structlog, and orjson. TRIGGERS - loguru, structlog, structured logging.