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 skills add testdouble/han --skill guidance-portablegit 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/guidance-portable)<a href="https://agentmods.dev/skills/testdouble/han/guidance-portable"><img src="https://agentmods.dev/badge/skills/testdouble/han/guidance-portable/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/guidance-portable"><img src="https://agentmods.dev/badge/skills/testdouble/han/guidance-portable.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.00095 | $0.00575 |
| Opus 5.5 | $0.00038 | $0.00230 |
| Sonnet 5.5 | $0.00019 | $0.00115 |
| Haiku 4.5 | $0.00010 | $0.00057 |
Grade A, and why
guidance 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
Serve the relevant guidance for what the user is building. Do not read every guidance document — that defeats the purpose. Find the one or two that apply, read them, and apply them.
The guidance documents live in this skill's own references/ directory. Use this map to choose, then read only the
specific file(s) you need:
- Deciding whether something should be a skill, agent, or hook →
${CLAUDE_SKILL_DIR}/references/plugin-entity-taxonomy.md. - Authoring or hardening a skill (descriptions, frontmatter, progressive disclosure, allowed-tools, scripts,
composition, testing, troubleshooting) → the files under
${CLAUDE_SKILL_DIR}/references/skill-building-guidance/. - Authoring an agent (domain focus, self-containment, model selection, multi-agent economics, graceful degradation) →
the files under
${CLAUDE_SKILL_DIR}/references/agent-building-guidelines/. - Plugin or marketplace configuration files (plugin.json, marketplace.json, monitors.json, themes.json) → the files
under
${CLAUDE_SKILL_DIR}/references/claude-marketplace-and-plugin-configuration/. - Versioning, README structure, local development, the iterative development process, and
specialization-versus-model-tier reasoning → the top-level files in
${CLAUDE_SKILL_DIR}/references/. - Writing the instructions for a target model (how Sonnet 5, Opus 5, and Fable 5 differ in following instructions, which
instructions to leave out, and how to calibrate length, narration, and scope) →
${CLAUDE_SKILL_DIR}/references/per-model-authoring.md. - Copyable starter files →
${CLAUDE_SKILL_DIR}/references/templates/.
Steps:
- Identify what the user is building or asking about.
- List the relevant subdirectory under
${CLAUDE_SKILL_DIR}/references/to see the available documents, using the map above. - Read only the document(s) that directly apply.
- Apply the guidance to the user's situation. Cite the document you used so the user can read it in full if they want.
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 · 39 lines · 95 tokens per session scan A 4a9342e22f2e
guidance is a skill published in the GitHub repository testdouble/han (316 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 575 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.