Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add testdouble/han/plugin install han-atlassianWrote 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/investigate-to-confluence)<a href="https://agentmods.dev/skills/testdouble/han/investigate-to-confluence"><img src="https://agentmods.dev/badge/skills/testdouble/han/investigate-to-confluence/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/testdouble/han/investigate-to-confluence"><img src="https://agentmods.dev/badge/skills/testdouble/han/investigate-to-confluence.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.00153 | $0.02155 |
| Opus 5 | $0.00077 | $0.01077 |
| Sonnet 5 | $0.00031 | $0.00431 |
| Haiku 4.5 | $0.00015 | $0.00215 |
Grade A, and why
investigate-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 9d 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 — 131 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.
Investigate to Confluence
This skill runs an evidence-based investigation with the core han-coding:investigate skill, lets the user review the
resulting report, and then publishes it to a Confluence location that the user must specify. It is a thin
orchestrator: the investigation work belongs to han-coding:investigate, and the publishing work belongs to
han-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the investigation to a temporary
file, gets the user's review and publish choice, and hands the file to the publisher.
han-coding:investigate produces a single report file (the investigation plan: problem statement, evidence summary,
root cause analysis, planned fix, validation results, and summary). It does not produce companion artifacts, so this
skill publishes that one file as a single Confluence page — the single-page sibling of
han-atlassian:project-documentation-to-confluence, not the parent-plus-children tree of
han-atlassian:plan-a-feature-to-confluence.
The five steps below are the whole skill. It does not resolve Confluence pages or call the Confluence MCP create/update
tools itself; han-atlassian:markdown-to-confluence owns all of that.
Step 1: Validate Inputs
Confirm the skill has everything it needs before spending effort on an investigation:
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.
- 9d ago First seen · 131 lines · 153 tokens per session scan A d1b1c4a89ca4
investigate-to-confluence is a skill published in the GitHub repository testdouble/han (259 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 2,155 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
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
vet
Thorough codebase investigation that finds and fixes real problems. Maps architecture, scans every layer (structural, correctness, security, reliability, performance, hygiene), prioritized report with evidence, fix plan, executes collaboratively. A senior engineer doing a full review with authority to fix. Use when…
daily-prevention
Use this skill to help a developer keep day-to-day code simple, maintainable, and robust — through automatable prevention (linters, type checkers, static analysis, and — for what static analysis structurally can't catch — AI-assisted review skills) rather than after-the-fact fixes. Trigger on "how do I keep this…
verify-simplify
A final code-cleanup workflow that runs at the end of verification. It removes repeated or unnecessary logic after the other verification steps are complete.
phx-challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
lsp-investigate
Investigate code using LSP tools. Register a project, then use definitions, references, call hierarchies, type hierarchies, hover, and diagnostics to understand code structure, trace bugs, and assess change impact.