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-coding)<a href="https://agentmods.dev/plugins/testdouble/han/han-coding"><img src="https://agentmods.dev/badge/plugins/testdouble/han/han-coding/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-coding"><img src="https://agentmods.dev/badge/plugins/testdouble/han/han-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
han-coding 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-coding",
"description": "Coding-facing skills for the Han suite: writing, reviewing, testing, investigating, and standardizing code. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate, and the refactor skill, which restructures existing code without changing its behavior through a test-gated refactoring loop, plus design-an-api (designing an interface contract for one stated goal through an options round, a question round, and an adversarial validation round), code-review (comprehensive review of local changes), code-overview (a progressive-disclosure, understand-now overview of unfamiliar code or a PR's changes), code-walkthrough (a paced, one-step-at-a-time walk through a branch's changes in conversation), architectural-analysis (module-level coupling, data flow, concurrency, risk, and SOLID assessment), automated-test-planning (coverage-gap and edge-case test plans), manual-test-planning (plain-language manual test plans a person runs by hand), investigate (evidence-based root-cause debugging), and coding-standard (creating and updating coding standards). Depends on han-core and han-communication; bundled by the han meta-plugin.",
"version": "3.4.0",
"dependencies": ["han-communication", "han-core"]
}
What it installs
The manifest is a name and a version. 11 skills travel with it, and installing the plugin installs all of them — 1,984 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill code-overview A 214 tokens
- Skill code-review A 147 tokens
- Skill design-an-api A 203 tokens
- Skill architectural-analysis A 190 tokens
- Skill automated-test-planning A 146 tokens
- Skill tdd A 224 tokens
- Skill code-walkthrough A 190 tokens
- Skill investigate A 170 tokens
- Skill manual-test-planning A 201 tokens
- Skill refactor A 203 tokens
- Skill coding-standard B 96 tokens
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 Changed e0377d0f0e10
- 1mo ago First seen · 7 lines scan A e2cee385195c
han-coding is a plugin published in the GitHub repository testdouble/han (304 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
rageatc-code-oss
Scale-adaptive software development — TDD, verification, perspective-based review, interface design, and tool capabilities (browser automation, PDFs, YouTube transcripts, local-LLM and Codex delegation).
craft-skills
Skills for code you'll have to live with. Two collections: craft (code that's understandable, named well, lean, loud about failure, and testable — without turning every edit into a rewrite) and rigor (claims you can believe — adversarial testing, full-suite banking, cited numbers, population sweeps, evidence-backed…
odoo-superpowers
Odoo SA development skills, hooks, and conventions for PSDU customer work. Principles-first guidance for module development, code review, testing, and continuous skill refinement.
crap-analyzer
Analyze recently-changed code for Change Risk Anti-Patterns. Computes CRAP per changed function across TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, and PHP. Auto-discovers how the repo generates coverage and proposes refactors + test stubs.
fuse-ai-pilot
AI Pilot workflow agents: sniper (code quality), research-expert, explore-codebase, websearch.
superpowers-orchestrator
Agentic development framework for Claude Code — disciplined workflow routing, TDD enforcement, safety hooks, systematic debugging, and code review.