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/commands/freema/mcp-jira-stdio/search)<a href="https://agentmods.dev/commands/freema/mcp-jira-stdio/search"><img src="https://agentmods.dev/badge/commands/freema/mcp-jira-stdio/search/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/commands/freema/mcp-jira-stdio/search"><img src="https://agentmods.dev/badge/commands/freema/mcp-jira-stdio/search.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.00006 | $0.00147 |
| Opus 5.5 | $0.00002 | $0.00059 |
| Sonnet 5.5 | $0.00001 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
search 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
/jira:search
Search for Jira issues using JQL (Jira Query Language).
Usage
/jira:search <jql-query>
Examples
/jira:search project = MYPROJ AND status = "To Do"
/jira:search assignee = currentUser() ORDER BY updated DESC
/jira:search labels = bug AND priority = High
/jira:search sprint in openSprints()
What Happens
Calls jira_search_issues with the JQL query and returns matching issues with key, summary, status, assignee, and priority.
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 · 28 lines · 6 tokens per session scan A e5d8f905af17
search is a command published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 24d ago), licensed MIT. It adds 6 tokens to every session and 147 once invoked, about $0.0000 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 commands, from other repositories
implement-plan
Implement the plan as specified, it is attached for your reference. Do NOT edit the plan file itself. Create todos for the plan as you work, starting with the first one. Don't stop until you have completed all the to-dos.
project
Command "project" from getsentry/sentry-mcp, covering examples, list all projects in an org, filter by platform, view project details and open project in browser.
org
Command "org" from getsentry/sentry-mcp, covering examples, list organizations, view organization details, open in browser and json output.
trial
Command "trial" from getsentry/sentry-mcp, covering examples, list all trials for the current org, list trials for a specific org, start a seer trial and start a trial for a specific org.
plan-backlog
Turn an idea, brief, or document into a well-formed backlog and create it in your tracker after approval. Guided by default; --quick for a one-shot draft. Usage - /plan-backlog [--quick].
plan-definition
Turn a spark (an idea, even a one-liner) into a clear product definition through a guided discovery phase, then hand it to plan-backlog. Facilitate, never decide. Usage - /plan-definition.