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-writegit 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-write)<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/jira-write"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/jira-write/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-write"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/jira-write.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.00038 | $0.00532 |
| Opus 5 | $0.00019 | $0.00266 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
jira-write 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 9d 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 Write Skill
Write operations for creating and modifying Jira data.
Allowed Operations
- Create issues
- Update issue fields
- Add comments
- Transition issues between statuses
- Move issues to sprints
- Update sprint details
- Link issues
Forbidden Operations
- Delete issues (requires separate approval)
- Bulk operations without explicit approval
- Modifying project settings
- User management
- Permission changes
Constraints
- All write operations support dry-run mode
- Each operation must be atomic
- Maximum 10 operations per batch
Dry-Run Mode
Always recommend dry-run first for important changes:
{
"issueKey": "PROJ-123",
"summary": "New title",
"dryRun": true
}
When dryRun: true:
- Validates all inputs
- Checks permissions
- Returns what WOULD happen
- Makes NO changes
Quick Reference
Create Issue
{
"projectKey": "PROJ",
"summary": "Issue title",
"issueTypeName": "Bug",
"priority": "High"
}
Update Issue
{
"issueKey": "PROJ-123",
"summary": "Updated title",
"labels": ["urgent"]
}
Transition Issue
{
"issueKey": "PROJ-123",
"transitionName": "Done"
}
For detailed transition workflows, see TRANSITIONS-GUIDE.md.
For complete field formats and custom fields, see FIELD-REFERENCE.md.
Error Handling
| Scenario | Action |
|---|---|
| Validation failure | Return all errors at once |
| Permission denied | Clear message, no retry |
| Conflict | Return current state |
Example Usage
Create a bug in project API with high priority
Update PROJ-123 to add acceptance criteria
Transition PROJ-456 to In Review
Move issues PROJ-1, PROJ-2 to Sprint 5
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.
- 9d ago First seen · 107 lines · 38 tokens per session scan A d9e6b16bcd9d
jira-write is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 532 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.
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.
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.
monorepo
Monorepo management (Nx, Turborepo, pnpm workspaces) — task orchestration, caching, code sharing. Use when setting up monorepo, optimizing builds, or managing multi-package projects.