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 skills/kolodkin/devpowers/jira-ticketnpx skills add kolodkin/devpowers --skill jira-ticketgit clone --depth 1 https://github.com/kolodkin/devpowersWrote 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/kolodkin/devpowers/jira-ticket)<a href="https://agentmods.dev/skills/kolodkin/devpowers/jira-ticket"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/jira-ticket.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.00187 | $0.03168 |
| Opus 5 | $0.00093 | $0.01584 |
| Sonnet 5 | $0.00037 | $0.00634 |
| Haiku 4.5 | $0.00019 | $0.00317 |
Grade A, and why
jira-ticket 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.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Ticket — Create, Comment, or Update Description
Three modes, one content engine. The presence of a Jira issue key in the arguments (and whether description is also passed) determines the mode.
Validate env vars
Before parsing arguments or doing any Jira work, run this exact command to check the environment:
echo "JIRA_URL=${JIRA_URL:-NOT_SET}" && \
echo "JIRA_USERNAME=${JIRA_USERNAME:-NOT_SET}" && \
echo "JIRA_API_TOKEN=${JIRA_API_TOKEN:+SET}" && \
echo "JIRA_PERSONAL_TOKEN=${JIRA_PERSONAL_TOKEN:+SET}" && \
echo "JIRA_PROJECT_KEY=${JIRA_PROJECT_KEY:-NOT_SET}" && \
echo "JIRA_BOARD_ID=${JIRA_BOARD_ID:-NOT_SET}"
Required for any run:
JIRA_URLis set- Auth is set: either
JIRA_USERNAME+JIRA_API_TOKEN(Cloud) orJIRA_PERSONAL_TOKEN(Server / Data Center) JIRA_PROJECT_KEYis set- The
mcp__mcp-atlassian__jira_create_issuetool is visible in your tool list (i.e. themcp-atlassianserver is registered)
Required only if the user passed a sprint argument (current, sprint, next):
JIRA_BOARD_IDis set
If anything required is missing, tell the user one line — "Jira isn't fully configured; running /jira-setup to fix what's missing." — then invoke the jira-setup skill via the Skill tool. After setup completes, re-run this validation. Only proceed once everything required is green.
If the jira-setup skill isn't available in this session for any reason, fall back to instructing the user: "Run /jira-setup and then re-run /jira-ticket."
Parsing Arguments
/jira-ticket [args] — parse the comma-separated arguments to determine the mode.
The Jira issue key pattern in this skill is ${JIRA_PROJECT_KEY}-\d+ (e.g., if JIRA_PROJECT_KEY=PROJ, then PROJ-1234).
Mode Detection
- If any standalone argument exactly matches the issue key pattern:
- If
descriptionis also passed as an argument → enter Update Description Mode - Otherwise → enter Comment Mode
The entire trimmed argument must be the issue key — ignore keys that appear as part of other arguments (e.g.,
epic PROJ-1234is an epic linking argument, not a comment target).
- If
- Otherwise, enter Create Mode
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 · 286 lines · 187 tokens per session scan A d2f822079748
jira-ticket is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 26d ago), licensed MIT. It adds 187 tokens to every session and 3,168 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…