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-lifecyclegit 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-lifecycle)<a href="https://agentmods.dev/skills/grandcamel/jira-assistant-skills/jira-lifecycle"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-lifecycle/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-lifecycle"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 123 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00029 | $0.02379 |
| Opus 5 | $0.00015 | $0.01189 |
| Sonnet 5 | $0.00006 | $0.00476 |
| Haiku 4.5 | $0.00003 | $0.00238 |
Grade A, and why
jira-lifecycle-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-lifecycle-management — 89% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-lifecycle
Workflow and lifecycle management for JIRA issues.
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| List transitions | - |
Read-only |
| List versions/components | - |
Read-only |
| Transition issue | ! |
Can transition back |
| Assign/unassign | ! |
Can reassign |
| Resolve issue | ! |
Can reopen |
| Reopen issue | ! |
Can resolve again |
| Create version/component | - |
Easily reversible |
| Update version/component | ! |
Can be undone |
| Release version | ! |
Can unrelease |
| Archive version | ! |
Can unarchive |
| Delete component | !! |
Issues lose component association |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
Quick Discovery
Use this skill to: Drive issues through workflows, assign ownership, manage releases and components.
Not for: Creating/editing issue content (use jira-issue) or finding issues (use jira-search).
Also see: Workflow Guide | JSM Workflows | Best Practices
What this skill does
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
7 command categories for complete lifecycle management:
| Category | Purpose | Example |
|---|---|---|
| Transitions | Move issues between statuses | jira-as lifecycle transition PROJ-123 --to "In Progress" |
| Assignments | Control ownership | jira-as lifecycle assign PROJ-123 --self or --user email |
| Resolution | Mark issues complete | jira-as lifecycle resolve PROJ-123 --resolution Fixed |
| Reopen | Restore resolved issues | jira-as lifecycle reopen PROJ-123 |
| Versions | Plan and track releases | jira-as lifecycle version create PROJ --name "v2.0.0" |
| Components | Organize by subsystem | jira-as lifecycle component create PROJ --name "API" |
| Discovery | View available options | jira-as lifecycle transitions PROJ-123 |
What ships with it
11 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 3.8 KB
- docs/DAILY_OPERATIONS.md 8.6 KB
- docs/WORKFLOW_DESIGN.md 8.9 KB
- examples/LIFECYCLE_EXAMPLES.md 6.3 KB
- references/jsm_workflows.md 11 KB
- references/patterns/incident_workflow.md 2.9 KB
- references/patterns/jsm_request_workflow.md 2.7 KB
- references/patterns/software_dev_workflow.md 2.8 KB
- references/patterns/standard_workflow.md 1.7 KB
- references/TROUBLESHOOTING.md 5.9 KB
- references/workflow_guide.md 8.8 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 · 211 lines · 29 tokens per session scan A 8f13551e4020
jira-lifecycle-management is a skill published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 2,379 once invoked, about $0.0001 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.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.