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.
git 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/plugins/testdouble/han/han-atlassian)<a href="https://agentmods.dev/plugins/testdouble/han/han-atlassian"><img src="https://agentmods.dev/badge/plugins/testdouble/han/han-atlassian/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/plugins/testdouble/han/han-atlassian"><img src="https://agentmods.dev/badge/plugins/testdouble/han/han-atlassian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
han-atlassian 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.
What it actually says
{
"name": "han-atlassian",
"description": "Atlassian-facing extensions to the Han suite. Adds markdown-to-confluence, which publishes a local Markdown file to a user-specified Confluence page; project-documentation-to-confluence, which runs the han-documentation project-documentation skill and then publishes the result there; investigate-to-confluence, which runs the core investigate skill and publishes the resulting investigation report there; code-overview-to-confluence, which runs the core code-overview skill and publishes the resulting overview there; plan-a-feature-to-confluence, which runs the plan-a-feature planning skill and publishes the spec and its companion artifacts there as a page tree; and work-items-to-jira, which creates one Jira ticket per slice from a work-items file. All work through the Atlassian MCP server. Depends on han-core, han-documentation, han-planning, and han-coding (its wrapper skills run skills from each and its wrapped skills dispatch the shared han-core agents), and on han-communication (its wrapped prose-producing skills source the shared readability standard), and requires a configured Atlassian MCP server. Opt-in: installed on its own, not pulled in by the han meta-plugin.",
"version": "2.3.1",
"dependencies": ["han-communication", "han-core", "han-documentation", "han-planning", "han-coding"]
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 901 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 7 lines scan A 4e18e0c9c588
han-atlassian is a plugin published in the GitHub repository testdouble/han (311 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
fuse-ai-pilot
AI Pilot workflow agents: sniper (code quality), research-expert, explore-codebase, websearch.
alon-skills
Architecture, code review, prompting, and decision-making skills tuned to Alon Baron's engineering style: model-first, failure-path-aware, YAGNI. v3: six skills rewritten for Claude Fable 5.1 as judgment rules, a build-loop workflow that builds TODOWORKFLOW.md rows unattended, a claude plugin eval suite, and (3.1) a t.
The control plane for game-dev agents — close the loop with verified compile, test, and cross-model review across Unity, Godot, Unreal, and S&box. Lifecycle-aware /qq:go routing, structured runtime state in .qq/, 28 /qq: slash commands. Claude Code-first, agent-agnostic via MCP and plain shell / Python scripts.
ottonomous
Four independent, provider-agnostic skills for product specification, code review, spec-driven implementation, and Moss change summaries.
fable-super-audit
Comprehensive, rubric-driven, whole-repository code audit that ends in a prioritized improvement plan with an executive health grade.
jeff
Meet your new sous chef, Jeff: a model-native quality control plane and cooperative workflow protocol for trusted operators and friendly agents, not a security sandbox.