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 thammarongg/jira-mcp --skill skillgit clone --depth 1 https://github.com/thammarongg/jira-mcpWrote 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/thammarongg/jira-mcp/skill)<a href="https://agentmods.dev/skills/thammarongg/jira-mcp/skill"><img src="https://agentmods.dev/badge/skills/thammarongg/jira-mcp/skill/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/thammarongg/jira-mcp/skill"><img src="https://agentmods.dev/badge/skills/thammarongg/jira-mcp/skill.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.00070 | $0.02269 |
| Opus 5 | $0.00035 | $0.01135 |
| Sonnet 5 | $0.00014 | $0.00454 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
jira 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 8d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira (via jira-mcp MCP server)
The jira MCP server exposes the full Jira REST API: boards, sprints,
epics, issues (JQL, transitions, comments, worklogs), projects, users, and a
raw jira_api passthrough for any /rest/... endpoint. Works with Jira
Cloud (API v3) and Data Center (API v2); field-shape differences are handled
server-side.
If the jira MCP tools are not available
Tell the user the server isn't configured and offer to set it up. Easiest is
the interactive installer (writes config for the selected agents — Claude
Code, OpenCode, Codex, Cursor, Claude Desktop, Gemini CLI; backs up existing
files to .bak):
npx -y @thammarongg/jira-mcp@latest install
Or non-interactive: npx -y @thammarongg/jira-mcp@latest install --agents all --base-url https://your-org.atlassian.net --email [email protected] --token xxx --yes. Required env vars:
JIRA_BASE_URL—https://your-org.atlassian.net(Cloud) orhttps://jira.yourcompany.com(DC); a DC context path such as/jirais supported and preserved- Cloud:
JIRA_EMAIL+JIRA_API_TOKEN(token from id.atlassian.com → Security → API tokens) - DC:
JIRA_USERNAME+JIRA_API_TOKEN(PAT) orJIRA_PASSWORD(app password)
When a selected agent already has a jira entry, the interactive installer
offers to reuse its base URL and account; --yes with no credential flags
reuses those credentials without prompting.
The CLI also supports these maintenance commands:
npx -y @thammarongg/jira-mcp@latest update # refresh configured entries
npx -y @thammarongg/jira-mcp@latest update --agents codex
npx -y @thammarongg/jira-mcp@latest uninstall # choose entries to remove
npx -y @thammarongg/jira-mcp@latest uninstall --agents all --yes
npx -y @thammarongg/jira-mcp@latest --version
npx -y @thammarongg/jira-mcp@latest --help
update is non-interactive and skips agents without a jira entry.
uninstall preserves every other config key and confirms before removing the
selected entries unless --yes is supplied. Running the command with no
arguments in a terminal shows a status card; MCP clients use piped stdio, so
the same command starts the server and expects JIRA_* environment variables.
Without those variables, a bare server start reports a missing
JIRA_BASE_URL.
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.
- 8d ago First seen · 175 lines · 70 tokens per session scan A f40d7f4d72de
jira is a skill published in the GitHub repository thammarongg/jira-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 70 tokens to every session and 2,269 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-31.
Other skills, from other repositories
pm-skills
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it…
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
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-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-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)…