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 quatico-solutions/agent-skills --skill working-with-jira-webgit clone --depth 1 https://github.com/quatico-solutions/agent-skillsWrote 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/quatico-solutions/agent-skills/working-with-jira-web)<a href="https://agentmods.dev/skills/quatico-solutions/agent-skills/working-with-jira-web"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/working-with-jira-web/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/quatico-solutions/agent-skills/working-with-jira-web"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/working-with-jira-web.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.00052 | $0.01511 |
| Opus 5 | $0.00026 | $0.00756 |
| Sonnet 5 | $0.00010 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
working-with-jira-web 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with JIRA
This skill covers JIRA ticket operations with two approaches:
- Atlassian MCP (primary) — fast, reliable API access
- Browser automation (fallback) — for visual verification or missing API features
Tool Selection Decision Tree
Need to interact with JIRA?
├── Create/Read/Update ticket? → Atlassian MCP
├── Search tickets (JQL)? → Atlassian MCP
├── Add comment? → Atlassian MCP
├── Visual verification needed? → Browser automation
├── Feature not in API? → Browser automation
└── Debug why MCP failed? → Browser automation
| Operation | Recommended Tool | Why |
|---|---|---|
| Create ticket | MCP createJiraIssue |
Single API call, markdown description |
| Update description | MCP editJiraIssue |
Markdown input, instant update |
| Read ticket | MCP getJiraIssue |
Full data, no UI parsing |
| Search (JQL) | MCP searchJiraIssuesUsingJql |
Structured results |
| Add comment | MCP addCommentToJiraIssue |
Markdown, no WYSIWYG |
| Link tickets | MCP or Browser | MCP limited, browser more flexible |
| Visual verification | Browser | See rendered result |
Atlassian MCP (Primary)
Authentication
- Run
/mcpin Claude Code - Select atlassian from the list
- Complete OAuth flow in browser
- Sessions expire periodically — re-run
/mcpif you get auth errors
Key Tools
| Tool | Purpose |
|---|---|
getJiraIssue |
Fetch ticket details |
editJiraIssue |
Update ticket fields (description accepts markdown!) |
createJiraIssue |
Create new ticket |
addCommentToJiraIssue |
Add comment (markdown) |
searchJiraIssuesUsingJql |
Search using JQL |
getTransitionsForJiraIssue |
Get available status transitions |
transitionJiraIssue |
Change ticket status |
CloudId Discovery
Most tools require cloudId. Get it from search results or use getAccessibleAtlassianResources.
Example: Update Description
mcp__plugin_atlassian_atlassian__editJiraIssue({
cloudId: "your-cloud-id",
issueIdOrKey: "EWZREL-123",
fields: {
description: "## Overview\n\nThis ticket tracks...\n\n- Item 1\n- Item 2\n\n### Technical Details\n\n```\ncode block here\n```"
}
})
What ships with it
1 file 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.
- 11d ago First seen · 185 lines · 52 tokens per session scan A 0182bb03bb7f
working-with-jira-web is a skill published in the GitHub repository quatico-solutions/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 1,511 once invoked, about $0.0003 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
daily-working
End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…
wfdash
Serve wayfinder maps held in GitHub Issues as a local browser dashboard — one map drawn as a dependency DAG, plus an overview of every map across every repo. Use when the user asks what to work on next, wants to see a map's shape or frontier, wants to read a resolved ticket's decision, or types /wfdash. Also use for…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…