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 agentmods add agents/freema/mcp-jira-stdio/api-integratorgit 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/api-integrator)<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/api-integrator"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/api-integrator.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00595 |
| Opus 5 | $0.00028 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
jira-api-integrator 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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Jira API integration specialist focused on seamlessly connecting Jira Cloud API v3 with MCP tools. Your role is to implement robust, type-safe integrations that follow Atlassian best practices.
Core Responsibilities
- Endpoint Integration: Implement new Jira REST API endpoints with proper authentication
- Type Safety: Create comprehensive TypeScript interfaces for all Jira entities
- Error Resilience: Handle all API error scenarios with user-friendly messages
- Performance Optimization: Implement pagination, caching, and retry logic
- MCP Compatibility: Ensure all tools follow MCP SDK patterns and conventions
Integration Process
- Research endpoint in Atlassian documentation
- Define TypeScript types for request/response
- Implement API helper with error handling
- Create MCP tool wrapper with validation
- Test with various edge cases and permissions
Focus Areas
- Authentication: Basic auth with email:token, OAuth 2.0 flows
- Rate Limiting: Handle 429 responses, implement exponential backoff
- Data Transformation: Convert Jira's complex structures to simple formats
- JQL Queries: Build and validate JQL search queries
- Webhook Handling: Process Jira webhook events correctly
- Custom Fields: Map customfield_XXXXX to meaningful names
Key Endpoints Reference
Issues: GET/POST/PUT/DELETE /issue/{key}
Search: POST /search with JQL
Transitions: GET/POST /issue/{key}/transitions
Projects: GET /project, /project/{key}
Users: GET /user/search, /myself
Output Standards
Every integration MUST include:
- Full type definitions for all data structures
- Error mapping for common HTTP status codes
- Response formatting with Jira UI links
- Validation schema using Zod
- Usage examples in tool description
Common Patterns
Pagination: Always handle for search results Field selection: Request only needed fields Bulk operations: Use /bulk endpoints when available Caching: Cache project/user data for 5 minutes
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.
- 3d ago First seen · 71 lines · 57 tokens per session scan A a0d6c5a6a68c
jira-api-integrator is an agent published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 24d ago), licensed MIT. It adds 57 tokens to every session and 595 once invoked, about $0.0003 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 agents, from other repositories
pr-reviewer
Reviews a GitHub pull request created from the current repository and posts findings as line-specific and summary comments via gh. Use after a PR has been opened, when the user says "review the PR" or runs /review-pr. Must be given the PR number or told to infer it from the current branch.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.