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-developer-integrationgit 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-developer-integration)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/jira-developer-integration"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/jira-developer-integration/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-developer-integration"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/jira-developer-integration.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.00113 | $0.02196 |
| Opus 5 | $0.00056 | $0.01098 |
| Sonnet 5 | $0.00023 | $0.00439 |
| Haiku 4.5 | $0.00011 | $0.00220 |
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 7d 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
88% identical to jira-developer-integration — 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 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 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.
- 7d ago First seen · 238 lines · 113 tokens per session scan A f194da7e738b
jira-developer-integration is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 2,196 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to jira-developer-integration, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
omh-github-issue-intake
This is a Hermes-native github-issue-intake workflow skill.
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.
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'…
claim
Acquire, renew or release a Fakoli State task lease when beginning work or recovering an interrupted claim.
workspace-standards
Use when setting up or managing multi-repo workspaces.
git-commit-conventional
Create Conventional Commit messages and execute safe git commits from working tree changes. Use when users ask to create a commit, write a conventional commit message, split broad changes into multiple commits, stage only parts of files, run pre-commit before committing, or perform a quick commit-time quality review…