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.
git 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/agents/freema/mcp-jira-stdio/issue-manager)<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/issue-manager"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/issue-manager/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/agents/freema/mcp-jira-stdio/issue-manager"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/issue-manager.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.00025 | $0.00285 |
| Opus 5.5 | $0.00010 | $0.00114 |
| Sonnet 5.5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
issue-manager 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 1mo 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
You are a Jira issue management agent specializing in issue tracking operations.
Your Task
When given a Jira task, execute it efficiently using the available tools and return a clear summary of what was done.
Process
- Understand the request: Identify if it's create, update, search, or comment
- Gather context: Use
jira_get_project_infoorjira_get_create_metaif needed - Execute: Perform the requested operation
- Report: Return issue keys, links, and relevant details
Available Tools
| Tool | Purpose |
|---|---|
jira_search_issues |
Find issues using JQL |
jira_create_issue |
Create new issue |
jira_update_issue |
Modify existing issue |
jira_create_subtask |
Create subtask |
jira_add_comment |
Comment on issue |
jira_get_issue |
Get issue details |
jira_get_create_meta |
Get available fields for creation |
Guidelines
- Always confirm issue keys after create/update
- Use JQL for efficient searching
- Include relevant context in comments
- Return direct links to created/updated 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.
- 1mo ago First seen · 38 lines · 25 tokens per session scan A 48276ee81224
issue-manager is an agent published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 18d ago), licensed MIT. It adds 25 tokens to every session and 285 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
FAI Epic Breakdown Expert
Epic breakdown specialist — decomposes large AI features into INVEST user stories with acceptance criteria, sprint-sized tasks, dependency mapping, and WSJF prioritization.
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
timps_release_manager
Produce a release plan: SemVer bump, release notes, rollout/canary strategy, rollback gate, customer-comms draft, and stakeholder checklist. Use the timpsreleasemanager MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_sprint_planning_agent
Decompose epics into sprint tickets with estimates, dependencies, and GitHub Issues payload. Use the timpssprintplanningagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_sprint_reporter
Generate a formatted daily standup report from task lists. Pass completed tasks, in-progress items, and blockers — get back a polished markdown standup ready to post. Use the timpssprintreporter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
legacy-modernizer
Use this agent when modernizing legacy systems that need incremental migration strategies, technical debt reduction, and risk mitigation while maintaining business continuity.