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.
/plugin marketplace add testdouble/hannpx agentmods add plugins/testdouble/han/han-atlassiangit clone --depth 1 https://github.com/testdouble/hanGrade 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 2d 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 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.
- 2d ago First seen · 7 lines scan A 4e18e0c9c588
han-atlassian is a plugin published in the GitHub repository testdouble/han (247 stars, last pushed 4d ago), 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
docpull
Pull public web sources into Claude Code. Indexes static and server-rendered sites as local Markdown with conditional-GET caching, then exposes them as MCP tools. Local, browser-free, no API keys.
trigger-tree
See which docs your AI actually discovers — local documentation telemetry for Claude Code.
slideops
Turn a repository into a slide deck, then find out the day it stops matching the code. Ships slideops (repo to deck, with citation-based freshness checking) and slides-to-pdf (any hash-navigated HTML deck to a verified PDF).
record-tutorial
Record screen and generate narrated tutorial videos with AI voice-over.
moxie-docs
Plugin marketplace listing 1 plugin: moxie-docs.
claude-code-engineering
Turn Claude Code into a team that has to prove it: 44 skills, 8 review agents, a validation router, and a knowledge layer where nothing is asserted without a check that could have failed.