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/plan-a-feature-to-confluencenpx skills add testdouble/han --skill plan-a-feature-to-confluencegit 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/plan-a-feature-to-confluence)<a href="https://agentmods.dev/skills/testdouble/han/plan-a-feature-to-confluence"><img src="https://agentmods.dev/badge/skills/testdouble/han/plan-a-feature-to-confluence.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.1 | $0.00154 | $0.03838 |
| Opus 5 | $0.00077 | $0.01919 |
| Sonnet 5 | $0.00031 | $0.00768 |
| Haiku 4.5 | $0.00015 | $0.00384 |
Grade A, and why
plan-a-feature-to-confluence 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 6d 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 — 213 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.
Plan a Feature to Confluence
This skill builds a feature specification with the core han-planning:plan-a-feature skill, lets the user review the
result, and then publishes it to a Confluence location that the user must specify. It is a thin orchestrator: the
planning work belongs to han-planning:plan-a-feature, and the publishing work belongs to
han-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the planning skill to a temporary
folder, gets the user's review and publish choice, and hands each file to the publisher.
han-planning:plan-a-feature produces a small set of files — the primary feature-specification.md plus companion
artifacts under artifacts/ (the decision log, the team findings, and a lazily-created technical-notes file). This
skill publishes the spec as a parent page and each companion artifact as a child page beneath it, so the whole
plan lands in Confluence as one small page tree. The files cross-reference each other with relative links that do not
resolve once each file is its own Confluence page. Because this skill decides every page's title up front, it rewrites
those cross-file links into Confluence title-based page-link macros (the
<ac:link><ri:page ri:content-title="..."/>…</ac:link> form; Step 5 gives the exact macro to emit, link body and all)
before creating any page — these resolve by title at view time, so no page URL or ID has to exist first. That collapses
publishing to a single create pass: there is no separate relink-and-update pass, and each page is created exactly
once.
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.
- 6d ago First seen · 213 lines · 154 tokens per session scan A bf08e58912ce
plan-a-feature-to-confluence is a skill published in the GitHub repository testdouble/han (256 stars, last pushed 4d ago), licensed MIT. It adds 154 tokens to every session and 3,838 once invoked, about $0.0008 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.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…