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 gigsmart/haiku-method --skill haiku-showgit clone --depth 1 https://github.com/gigsmart/haiku-methodWrote 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/gigsmart/haiku-method/haiku-show)<a href="https://agentmods.dev/skills/gigsmart/haiku-method/haiku-show"><img src="https://agentmods.dev/badge/skills/gigsmart/haiku-method/haiku-show.svg" alt="Measured on agentmods" 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.00074 | $0.00648 |
| Opus 5 | $0.00037 | $0.00324 |
| Sonnet 5 | $0.00015 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
haiku-show 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 8d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show
Open the ad-hoc review pane for the active intent.
What this does
Calls haiku_review_open (NOT haiku_review — that's the diff-review workflow at /haiku:haiku-gate-review). The tool spawns a session-scoped review URL pointing at the SPA, launches the browser, and returns immediately — it does NOT block. The pane is ad-hoc — it shows the standard review UI but swaps Approve for Done/Close so it never accidentally mutates workflow state. Keep working after calling it; the user reads the pane at their own pace and closes it with Done when finished.
Feedback the user leaves on the pane persists to disk as feedback files and routes through the normal fix-loop on the next haiku_run_next — nothing here waits on it. (Only an actual gate blocks: that's /haiku:haiku-pickup/haiku_run_next driving to a gate-typed stage, which the engine handles via haiku_await_gate, not this browse pane.)
How to invoke
Default — opens against the auto-resolved active intent (the current git branch's intent, or the single non-completed intent in .haiku/intents/ when there's exactly one):
haiku_review_open()
With explicit intent (when the user names one in the slash command, or when the branch doesn't match):
haiku_review_open({ intent: "<slug>" })
With explicit stage (to land directly on that stage without making the user navigate):
haiku_review_open({ intent: "<slug>", stage: "<stage>" })
Argument parsing
The skill argument is free-form text. Common shapes the user might pass:
/haiku:haiku-show— no args, auto-resolve intent/haiku:haiku-show <intent-slug>— open that intent/haiku:haiku-show <intent-slug> <stage>— open that intent and land on that stage/haiku:haiku-show <stage>— when only one active intent exists, treat as a stage hint
Parse positionally. If the first token matches a known intent slug in .haiku/intents/, use it as intent; otherwise treat it as stage. The second token (if present) is always stage.
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.
- 8d ago First seen · 51 lines · 74 tokens per session scan A 2f1b97661355
haiku-show is a skill published in the GitHub repository gigsmart/haiku-method (24 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 648 once invoked, about $0.0004 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
concentrate-forces
A decision-making method for situations where several tasks compete for limited time, attention, computing power, or budget.
mass-line
A method for collecting feedback and facts from multiple people or sources, turning them into a plan, and checking the plan with those affected.
workflows
A workflow guide for tasks that need several kinds of reasoning in sequence, such as research, finding the main conflict, choosing a small starting point, and planning sustained work.
protracted-strategy
A long-term planning method for difficult work that cannot be completed quickly, divided into stages with steady progress over time.
redteam-mindset
Red-team operator discipline — the mindset corrections that separate offensive testing from defensive WAPT. Built from authorized red-team work where conservative defaults caused multiple findings to be missed and one to be incorrectly retracted. Use at the START of any red-team engagement and again whenever feeling…
password-spray-methodology
End-to-end password spray playbook. User enumeration, lockout detection, password pattern generation, spray execution across all protocols, error code differentials, and engagement discipline. Unifies M365/Entra, Okta, Exchange, Kerberos, SharePoint, XMLRPC, OIDC, and AD SMB/WinRM spraying into one methodology.