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/testdouble/han/work-items-to-jiranpx skills add testdouble/han --skill work-items-to-jiragit clone --depth 1 https://github.com/testdouble/hanWrote 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/testdouble/han/work-items-to-jira)<a href="https://agentmods.dev/skills/testdouble/han/work-items-to-jira"><img src="https://agentmods.dev/badge/skills/testdouble/han/work-items-to-jira.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.00123 | $0.04140 |
| Opus 5 | $0.00062 | $0.02070 |
| Sonnet 5 | $0.00025 | $0.00828 |
| Haiku 4.5 | $0.00012 | $0.00414 |
Grade A, and why
work-items-to-jira 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 5d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
- personal config directory: !
bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude" - project .han/config.md: !
cat .han/config.md 2>/dev/null || echo ""
As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Work Items to Jira Tickets
Take an already-broken-down work-items.md file (produced by /plan-work-items) and publish each slice as a Jira
ticket in a single target project.
The breakdown work — drafting slices, assigning symbolic IDs, specifying dependencies, inventorying references — has already been done upstream. This skill's job is to validate the format, confirm the target, create one ticket per slice through the Atlassian MCP server, link the within-file dependencies, and place the tickets in the chosen column.
Rules
- Every slice posts into one Jira project. This skill does not split work across repos or projects. A
work-items.mdthat names multiple code repos still produces tickets in the single project you name; the repo prose is informational only. - Dependencies are within-file only. Every SYM named in a
Depends online must resolve to another slice in the same file. ADepends onthat names an unknown SYM is a format error to surface for repair. - Symbolic-ID prefixes: accept whatever the input uses. Any uppercase prefix shape is valid (
W-N,V2-N,EV-N, …); the prefix has no effect on Jira placement. - Defaults: issue type
Story, no assignee, reporter taken from the Atlassian MCP identity, and the project's initial status (Backlog). Each is overridable per run; nothing is assigned or moved unless asked. - Parenting is optional and determines the child issue type.
--parent <KEY>accepts an epic or a standard issue (a story, task, or bug). Under an epic, each item is a standard issue (defaultStory). Under a story (any standard issue), each item is a subtask (default the project's subtask issue type). You cannot parent under a subtask.--epic <KEY>is a deprecated alias for--parent; it resolves the same way regardless of the named issue's actual type. - Every slice ticket MUST carry the reference artifacts an implementer needs — API/event contracts, design references, schema docs, runbooks, ADRs, coding standards. Tickets that consume an HTTP endpoint or event payload MUST reference the contract section that defines it. Full include/exclude list in references/reference-artifact-inventory.md.
- NEVER include process artifacts in ticket descriptions. Excluded: iteration histories, decision logs, review
findings, team findings, facilitation summaries, gap analyses, and anything under an
artifacts/subfolder of the plan that is not a contract or design reference. - No screenshot upload or image embedding. Design references are carried as links, not uploaded into Jira. See references/jira-ticket-template.md.
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.
- 5d ago First seen · 243 lines · 123 tokens per session scan A 1dc14bc45639
work-items-to-jira is a skill published in the GitHub repository testdouble/han (256 stars, last pushed 4d ago), licensed MIT. It adds 123 tokens to every session and 4,140 once invoked, about $0.0006 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
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
phx-freeze
Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…