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 Yoshikemolo/mcp-jira-devflow --skill jira-readgit clone --depth 1 https://github.com/Yoshikemolo/mcp-jira-devflowWrote 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/yoshikemolo/mcp-jira-devflow/jira-read)<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/jira-read"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/jira-read/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/yoshikemolo/mcp-jira-devflow/jira-read"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/jira-read.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.00035 | $0.00451 |
| Opus 5 | $0.00017 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
jira-read 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 10d 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 Read Skill
Read-only operations for Jira data retrieval and analysis.
Allowed Operations
- Read issue by key (e.g.,
PROJECT-123) - Execute JQL queries
- Read issue metadata (fields, transitions, comments)
- Read issue changelog/history
- List projects and boards
- Read sprint information
- Get velocity metrics
Forbidden Operations
- Writing or updating issues
- Adding comments
- Transitioning issues
- Creating issues
- Deleting anything
Constraints
- Maximum 50 issues per query (use pagination for more)
- Rate limiting must be respected
- All requests require proper authentication
Input Requirements
- Issue keys:
[A-Z]+-\d+pattern (e.g., PROJ-123) - Project keys: uppercase alphanumeric
- JQL queries: validate before execution
Quick JQL Reference
# Common patterns
assignee = currentUser() AND status != Done
project = PROJ AND sprint IN openSprints()
created >= -7d AND priority = High
For detailed JQL syntax, operators, and examples, see JQL-CHEATSHEET.md.
Error Handling
| Status | Action |
|---|---|
| 404 | Issue not found - verify key |
| 401/403 | Auth error - check credentials |
| 429 | Rate limited - backoff and retry |
For complete error codes and retry strategies, see ERROR-HANDLING.md.
Example Usage
Get issue PROJ-123 with full details
Search for open bugs in project WEBAPP
Show sprint velocity for the last 5 sprints
Find issues assigned to me in current sprint
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 75 lines · 35 tokens per session scan A ccacd8548338
jira-read is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 451 once invoked, about $0.0002 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
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
monorepo
Monorepo management (Nx, Turborepo, pnpm workspaces) — task orchestration, caching, code sharing. Use when setting up monorepo, optimizing builds, or managing multi-package projects.