Borrowing it
Nothing to install: this file belongs to criblio/ultra-jira-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/criblio/ultra-jira-mcp/main/.claude/skills/jira-mcp-dev/SKILL.mdgit clone --depth 1 https://github.com/criblio/ultra-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/criblio/ultra-jira-mcp/jira-mcp-dev)<a href="https://agentmods.dev/skills/criblio/ultra-jira-mcp/jira-mcp-dev"><img src="https://agentmods.dev/badge/skills/criblio/ultra-jira-mcp/jira-mcp-dev/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/criblio/ultra-jira-mcp/jira-mcp-dev"><img src="https://agentmods.dev/badge/skills/criblio/ultra-jira-mcp/jira-mcp-dev.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.00076 | $0.01432 |
| Opus 5 | $0.00038 | $0.00716 |
| Sonnet 5 | $0.00015 | $0.00286 |
| Haiku 4.5 | $0.00008 | $0.00143 |
Grade A, and why
ultra-jira-mcp-dev 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 11d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ultra-jira-mcp contributor skill
You are working inside the ultra-jira-mcp repo (npm package name;
the binaries it ships are still jira-mcp and jira-cli). This
skill teaches the architecture and the toolkit boundary so you don't
have to re-derive them on every task.
For a longer prose version, see CLAUDE.md.
The three layers
Every Jira call flows through the same three layers — internalize this
before touching anything in src/:
- Manifest —
src/core/operations.tsdeclares the endpoint (path, HTTP verb, param roles, optionaltrimkey, optionalisAgile: true). - Dispatcher —
src/core/manifest.ts(invokeOperation) reads the manifest entry, builds the HTTP call viaJiraClient, sandboxes the full response, and applies the trim. - Surface — either a consolidated classic tool
(
src/tools/v2/<category>.ts— one per category, each aoneOfdispatcher) or the single code-api tool (src/codeapi/tool.ts), which hands the agent a path tojira-cliand a unix socket.
The CLI (src/cli/index.ts) is a fourth surface that reads the same
manifest — same dispatcher, same trims, no MCP server required.
Adding a new Jira operation
The common case. Steps, in order:
- Add a manifest entry in
src/core/operations.ts. Keep entries grouped by category section comment. Naming iscategory.verbwhere verb is logical, not HTTP (soissue.transition, notissue.post). - Add a trim if the response is bulky. Trims live in
src/core/trim.ts; register the key intrim-registry.ts. The trim's job is to produce the small object the agent sees on stdout — everything else gets written to disk and referenced viaref: /path. - Route the action from the relevant
src/tools/v2/<category>.tsdispatcher so classic-mode users get it. Code-api mode picks it up automatically from the manifest. - Tests: add a fixture-based test under
tests/core/for the trim and a smoke test undertests/tools/for the dispatcher path. Live Jira calls are not allowed in unit tests. - If the operation changes the tool-list size meaningfully
(new category, large new schema), run
npm run benchmarkand note the new numbers indocs/BENCHMARK.md.
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.
- 11d ago First seen · 140 lines · 76 tokens per session scan A eaf565d691b4
ultra-jira-mcp-dev is a skill published in the GitHub repository criblio/ultra-jira-mcp (5 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 1,432 once invoked, about $0.0004 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
scraperapi-nodejs-sdk
Best-practices reference for the ScraperAPI Node.js / JavaScript SDK (scraperapi-sdk npm package). Consult whenever the user is writing, debugging, or reviewing JavaScript or TypeScript code that calls ScraperAPI. Use when user asks: "scrape a website with Node.js and ScraperAPI", "ScraperAPI JavaScript example", "how…
connect-recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue…
ax-agent-rlm
This skill helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax. Use when the user asks about RLM code execution, AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, stage prompt controls, executorModelPolicy, maxRuntimeChars, agent.test(...), llmQuery(...), recursionOptions…
ax-llm
This skill helps with using the @ax-llm/ax TypeScript library for building LLM applications. Use when the user asks about ax(), ai(), f(), s(), agent(), flow(), AxGen, AxAgent, AxFlow, signatures, streaming, or mentions @ax-llm/ax.
ax-go-flow
Use when writing Go code with github.com/ax-llm/ax/packages/go for flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components.
ax-java-gen
Use when writing Java code with dev.axllm:ax for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.