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 freema/mcp-jira-stdio --skill jira-managementgit clone --depth 1 https://github.com/freema/mcp-jira-stdioWrote 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/freema/mcp-jira-stdio/jira-management)<a href="https://agentmods.dev/skills/freema/mcp-jira-stdio/jira-management"><img src="https://agentmods.dev/badge/skills/freema/mcp-jira-stdio/jira-management/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/freema/mcp-jira-stdio/jira-management"><img src="https://agentmods.dev/badge/skills/freema/mcp-jira-stdio/jira-management.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.00042 | $0.00438 |
| Opus 5 | $0.00021 | $0.00219 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
jira-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 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.
What it actually says
When the user asks about Jira or issue tracking, use the Jira MCP tools.
When to Use This Skill
Activate when the user:
- Wants to create issues ("Create a bug ticket", "File a story")
- Needs to search issues ("Find open bugs", "Show my tasks")
- Updates issues ("Change priority", "Assign to me", "Update status")
- Adds comments ("Comment on PROJ-123")
- Asks about projects ("List projects", "Show project info")
Tools Reference
| Task | Tool |
|---|---|
| Search issues | jira_search_issues (JQL) |
| Create issue | jira_create_issue |
| Update issue | jira_update_issue |
| Get issue | jira_get_issue |
| Add comment | jira_add_comment |
| Create subtask | jira_create_subtask |
| List projects | jira_get_visible_projects |
| My issues | jira_get_my_issues |
| Get metadata | jira_get_create_meta |
JQL Quick Reference
project = PROJ # Filter by project
status = "In Progress" # Filter by status
assignee = currentUser() # Your issues
priority = High # Filter by priority
sprint in openSprints() # Current sprint
labels = bug # Filter by label
ORDER BY updated DESC # Sort by updated
Example Workflows
Create a bug:
jira_get_create_meta project="PROJ" # Get available fields
jira_create_issue project="PROJ" issueType="Bug" summary="..." description="..."
Update and comment:
jira_update_issue issueKey="PROJ-123" priority="High"
jira_add_comment issueKey="PROJ-123" body="Updated priority based on..."
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 · 57 lines · 42 tokens per session scan A 75c78652d80d
jira-management is a skill published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 438 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-30.
Other skills, from other repositories
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
jira-service-management
Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.
jira-time-tracking
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…
jira-custom-fields
Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…
jira-issue-management
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…
jira-issue-relationships
Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue…