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 commands/freema/mcp-jira-stdio/creategit 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/create)<a href="https://agentmods.dev/commands/freema/mcp-jira-stdio/create"><img src="https://agentmods.dev/badge/commands/freema/mcp-jira-stdio/create.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.00005 | $0.00133 |
| Opus 5 | $0.00003 | $0.00067 |
| Sonnet 5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
create 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 4d 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:create
Create a new issue in Jira.
Usage
/jira:create <project-key> <issue-type> "<summary>"
Examples
/jira:create PROJ Bug "Login button not responding"
/jira:create PROJ Story "Implement dark mode"
/jira:create PROJ Task "Update dependencies"
What Happens
- Calls
jira_get_create_metato get available fields - Creates the issue with
jira_create_issue - Returns the new issue key and link
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.
- 4d ago First seen · 29 lines · 5 tokens per session scan A 00e42d11d0ed
create is a command published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 24d ago), licensed MIT. It adds 5 tokens to every session and 133 once invoked, about $0.0000 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 commands, from other repositories
context-new
Create a new GitHub repository with AllBeads pre-configured.
project-new
Plan a new project - create repo and beads, but don't code yet.
jira-discover-project
Discover JIRA project context for intelligent defaults and usage patterns.
ship
Encodes the "stage and commit" ritual: verify (receipt gate) → scope → branch → write the commit message from what is actually staged → commit → push → open PR to the default branch → move the Jira issue to In Review. NO merge (merging is the reviewer's call). NO tag (deploys are project-specific and out of scope).
ready
Find ready-to-work tasks across all contexts.
sync
Synchronize contexts with git remotes.