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 kolodkin/devpowers --skill jira-setupgit 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-setup)<a href="https://agentmods.dev/skills/kolodkin/devpowers/jira-setup"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/jira-setup/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/kolodkin/devpowers/jira-setup"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/jira-setup.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.00142 | $0.01751 |
| Opus 5.5 | $0.00057 | $0.00700 |
| Sonnet 5.5 | $0.00028 | $0.00350 |
| Haiku 4.5 | $0.00014 | $0.00175 |
Grade A, and why
jira-setup 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 1mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Setup
Walk through the steps below and prompt only for what's missing. Re-running this is safe — values that are already set are reported and skipped.
Step 0 — Ensure the mcp-atlassian MCP server is registered
This skill (and jira-ticket) drive Jira through the mcp__mcp-atlassian__* tools. Check whether mcp__mcp-atlassian__jira_create_issue is visible in your tool list.
-
If it's visible, the server is registered. Skip to Step 1.
-
If it's missing, hand off to the
setup-mcpskill, which is the bounded installer for this plugin's MCP servers —mcp-atlassianis already in its manifest. Invokesetup-mcpvia the Skill tool withmcp-atlassian(e.g./setup-mcp mcp-atlassian). It shows the proposed config, asks for scope, registers the server, and verifies theuvxprerequisite. Because MCP servers only load at startup, it will tell the user to restart Claude Code — so once it returns, tell the user to restart and re-run/jira-setup(or/jira-ticket), then stop. The tools won't be available until the restart.If the
setup-mcpskill isn't available in this session for any reason, fall back to instructing the user: "Run/setup-mcp mcp-atlassian, restart Claude Code, then re-run/jira-setup."
Step 1 — Validate credentials
Run this exact command:
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}"
JIRA_URL is always required. For auth, either the Cloud combo (JIRA_USERNAME + JIRA_API_TOKEN) or the Server / Data Center PAT (JIRA_PERSONAL_TOKEN) must be set. If neither is complete, instruct the user and stop. Do not proceed.
JIRA_URLisNOT_SET→ "Set your Jira workspace URL, e.g.export JIRA_URL=https://yourworkspace.atlassian.net"- Cloud (Atlassian-hosted,
*.atlassian.net): set bothJIRA_USERNAME→ your account email, e.g.export [email protected]JIRA_API_TOKEN→ create one at https://id.atlassian.com/manage-profile/security/api-tokens, thenexport JIRA_API_TOKEN=<your-token>
- Server / Data Center (self-hosted): set just
JIRA_PERSONAL_TOKEN→ create a Personal Access Token in your Jira profile, thenexport JIRA_PERSONAL_TOKEN=<your-pat>.JIRA_USERNAMEis optional here, but if you set it the jira-ticket skill will use it for the assignee / reporter on created tickets.
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.
- 1mo ago First seen · 123 lines · 142 tokens per session scan A af0f41d85c1b
jira-setup is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session and 1,751 once invoked, about $0.0006 per session on Opus 5.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
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…