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-devgit 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-dev)<a href="https://agentmods.dev/skills/grandcamel/jira-assistant-skills/jira-dev"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-dev/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-dev"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-dev.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.00113 | $0.01985 |
| Opus 5 | $0.00056 | $0.00992 |
| Sonnet 5 | $0.00023 | $0.00397 |
| Haiku 4.5 | $0.00011 | $0.00198 |
Grade A, and why
jira-developer-integration 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 11d 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-developer-integration — 88% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JIRA Developer Integration Skill
Developer workflow integration for JIRA including Git, CI/CD, and release automation.
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| Generate branch name | - |
Read-only, local output |
| Parse commits | - |
Read-only, local analysis |
| Get commits | - |
Read-only |
| Generate PR description | - |
Read-only, local output |
| Link commit | - |
Adds metadata, easily removed |
| Link PR | - |
Adds metadata, easily removed |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
Quick Start: Get started in 10 minutes
When to Use This Skill
Use this skill when you need to:
Starting Development:
- Generate standardized Git branch names from JIRA issues
- Create feature, bugfix, or hotfix branches with consistent naming
During Development:
- Extract JIRA issue keys from commit messages
- Link Git commits to JIRA issues via comments
- Log time and transition issues from commits (Smart Commits)
Code Review:
- Generate PR descriptions from JIRA issue details
- Link Pull Requests (GitHub, GitLab, Bitbucket) to JIRA issues
CI/CD Integration:
- Track builds and deployments in JIRA
- Auto-transition issues based on PR/deployment events
- Generate release notes from JIRA versions
Troubleshooting:
- Debug why Development Panel shows empty
- Fix Smart Commits not working
- Resolve PR linking issues
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
Available Commands
All commands support --help for full documentation.
| Command | Description |
|---|---|
jira-as dev branch-name |
Generate consistent branch names from issues |
jira-as dev parse-commits |
Extract issue keys from commit messages |
jira-as dev link-commit |
Link commits to JIRA issues |
jira-as dev get-commits |
Retrieve development information |
jira-as dev link-pr |
Automatically link PRs to JIRA |
jira-as dev pr-description |
Generate PR descriptions from issues |
What ships with it
16 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.3 KB
- docs/examples/github-actions-workflow.yml 4.1 KB
- docs/examples/gitlab-ci.yml 3.4 KB
- docs/examples/jenkins-pipeline.groovy 3.8 KB
- docs/examples/README.md 1.7 KB
- docs/guides/automation-rules.md 3.8 KB
- docs/guides/branch-naming.md 2.2 KB
- docs/guides/ci-cd-integration.md 3.3 KB
- docs/guides/commit-messages.md 2.5 KB
- docs/guides/common-pitfalls.md 4.3 KB
- docs/guides/deployment-tracking.md 3.4 KB
- docs/guides/development-panel.md 2.6 KB
- docs/guides/pr-workflows.md 2.5 KB
- docs/guides/release-notes.md 3.3 KB
- docs/guides/smart-commits.md 2.7 KB
- docs/QUICK_START.md 2.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.
- 11d ago First seen · 212 lines · 113 tokens per session scan A af2ecc064b44
jira-developer-integration is a skill published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 1,985 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-08-30.
Other skills, from other repositories
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
issue-create
Create well-formatted GitHub issues with intelligent AI-powered label suggestions and content type detection. Use whenever the user wants to.
get-up-to-speed
Reviews the latest git history, branch state, Linear ticket, and open work to build a concise situational summary. Use when picking up work after another agent, resuming a session, or onboarding to a branch mid-flight.
wrap-up
End-of-session handler that first checks whether the current session's plan is actually complete. If complete: run a quick retrospective, emit a forward-looking follow-up prompt, and — in a git repository — refresh the repo and clean gone branches. If incomplete: skip cleanup and emit ready-to-paste resume prompts so…
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.
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.