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 bmad-labs/skills --skill jira-to-localgit clone --depth 1 https://github.com/bmad-labs/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/bmad-labs/skills/jira-to-local)<a href="https://agentmods.dev/skills/bmad-labs/skills/jira-to-local"><img src="https://agentmods.dev/badge/skills/bmad-labs/skills/jira-to-local/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/bmad-labs/skills/jira-to-local"><img src="https://agentmods.dev/badge/skills/bmad-labs/skills/jira-to-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00183 | $0.03884 |
| Opus 5 | $0.00092 | $0.01942 |
| Sonnet 5 | $0.00037 | $0.00777 |
| Haiku 4.5 | $0.00018 | $0.00388 |
Grade A, and why
jira-to-local 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 12d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull a Jira issue into a local folder
One job: an issue key goes in, a folder of readable files comes out. One issue, one folder, everything in it — fields, comments, subtasks, worklogs, attachments, and any Confluence page the issue links to.
<skill-path> below is this skill's directory.
The seven rules
1. Pull only. This skill never creates, edits, transitions, comments on,
assigns, or deletes anything in Jira. Every request reads: every REST call is a GET,
and the one POST is a GraphQL query — the only way to read the deployment list,
which no REST endpoint serves. Nothing here mutates anything. If the user wants a
write, say so plainly and route to atlassian-rest — do not improvise it here.
2. Config first, and the config records the user's ticks. No
.jira.config.json means run workflows/setup.md before
anything else. Setup's five decisions — project, issue types, fields per type,
board, output — are the user's, and each is settled by a box in a file that
setup-choices.mjs generates from the API's own answer. The agent fetches the
options and records what the user did — never narrowing a list, summarising it, or
marking one option as recommended before they have seen all of it.
Only the starting state differs. Project, issue types, board and output arrive unticked, so a tick is the answer. A per-type fields file arrives fully ticked, because its options are the fields that issue type's screen shows — Jira's own answer to what the type holds — so keeping it all is the honest default and the user's job is to untick what they do not want. Either way their edit is the decision, and a fresh file is not one.
Setup also records one thing that is not a tick file: which of this site's custom
fields fills each metadata row (project.metaFields). Propose that mapping from the
field list already on screen, then let the user confirm it. An unmapped row is
written —, never guessed.
3. One part per call. fetch-issue.mjs writes one document per run. Never
reach for a single call that fetches everything: the parts are separate so each
can be checked while it is still small enough to check.
What ships with it
35 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.
- evals/evals.json 14 KB
- references/confluence-links.md 4.0 KB
- references/format-guide.md 7.4 KB
- references/jira-fields.md 16 KB
- references/output-json.md 5.4 KB
- references/refactor-guide.md 4.2 KB
- schemas/comments.schema.json 1.9 KB
- schemas/config.schema.json 9.5 KB
- schemas/content.schema.json 16 KB
- schemas/development.schema.json 12 KB
- schemas/tasks.schema.json 3.0 KB
- schemas/worklogs.schema.json 3.8 KB
- scripts/adf.mjs 10 KB runs code
- scripts/check-json.mjs 7.0 KB runs code
- scripts/check-markdown.mjs 9.5 KB runs code
- scripts/config.mjs 14 KB runs code
- scripts/confluence-format.mjs 19 KB runs code
- scripts/dev-status.mjs 16 KB runs code
- scripts/fetch-confluence.mjs 14 KB runs code
- scripts/fetch-issue.mjs 65 KB runs code
- scripts/inspect.mjs 17 KB runs code
- scripts/jira-api.mjs 11 KB runs code
- scripts/package.json 211 B
- scripts/setup-choices.mjs 21 KB runs code
- templates/comments.md 2.0 KB
- templates/confluence-page.md 1.7 KB
- templates/content.md 8.2 KB
- templates/development.md 6.2 KB
- templates/jira.config.json 1.5 KB
- templates/subagent-instruction.md 11 KB
- templates/tasks.md 2.7 KB
- templates/worklogs.md 2.6 KB
- workflows/bulk-pull.md 6.3 KB
- workflows/pull.md 9.6 KB
- workflows/setup.md 25 KB
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.
- 12d ago First seen · 240 lines · 183 tokens per session scan A f967dce692de
jira-to-local is a skill published in the GitHub repository bmad-labs/skills (15 stars, last pushed 16d ago), licensed MIT. It adds 183 tokens to every session and 3,884 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.