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 Yoshikemolo/mcp-jira-devflow --skill git-jira-integrationgit clone --depth 1 https://github.com/Yoshikemolo/mcp-jira-devflowWrote 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/yoshikemolo/mcp-jira-devflow/git-jira-integration)<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/git-jira-integration"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/git-jira-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/yoshikemolo/mcp-jira-devflow/git-jira-integration"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/git-jira-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.00032 | $0.00764 |
| Opus 5 | $0.00016 | $0.00382 |
| Sonnet 5 | $0.00006 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
git-jira-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git-Jira Integration Skill
Bridges Git workflows with Jira project management. Provides consistent naming, validation, and context generation to maintain traceability between code and issues.
Allowed Operations
- Link Git repositories to Jira projects
- Generate branch names from Jira issues
- Validate commit messages against conventions
- Generate PR context from Jira specifications
- List linked repositories
Forbidden Operations
These are NOT performed by this skill - agents have their own Git tools:
- Execute Git commands (clone, pull, push, commit)
- Create/merge Pull Requests directly
- Modify repository settings
- Access repository files or code
MCP Tools
| Tool | Purpose |
|---|---|
devflow_git_link_repo |
Link repository to Jira project |
devflow_git_get_repos |
List linked repositories |
devflow_git_branch_name |
Generate branch name from issue |
devflow_git_validate_commit |
Validate commit message format |
devflow_git_pr_context |
Generate PR title, body, checklist |
Constraints
- Branch names follow pattern:
{type}/{issueKey}-{slug} - Commit messages should follow Conventional Commits
- Commit messages should include issue key reference
- PR context requires existing Jira issues
Quick Reference
Branch Naming
Generate branch name:
devflow_git_branch_name(issueKey: "PROJ-123")
Result: feature/proj-123-add-user-authentication
Commit Validation
Validate commit message:
devflow_git_validate_commit(
message: "feat(auth): add login page\n\nRefs: PROJ-123",
projectKey: "PROJ",
requireIssueKey: true
)
PR Context
Generate PR context:
devflow_git_pr_context(
issueKeys: ["PROJ-123", "PROJ-124"],
includeAcceptanceCriteria: true
)
For detailed conventions, see BRANCH-CONVENTIONS.md.
For commit message format, see COMMIT-MESSAGE-FORMAT.md.
For PR templates, see PR-TEMPLATES.md.
What ships with it
4 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.
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.
- 9d ago First seen · 128 lines · 32 tokens per session scan A 2466c9abe2ea
git-jira-integration is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 764 once invoked, about $0.0002 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-31.
Other skills, from other repositories
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-issue-triage
Classify issues, draft a response, and produce a maintainers' queue update.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
omh-github-issue-intake
This is a Hermes-native github-issue-intake workflow skill.