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-zapgit 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-zap)<a href="https://agentmods.dev/skills/gigsmart/haiku-method/haiku-zap"><img src="https://agentmods.dev/badge/skills/gigsmart/haiku-method/haiku-zap/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/gigsmart/haiku-method/haiku-zap"><img src="https://agentmods.dev/badge/skills/gigsmart/haiku-method/haiku-zap.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.00029 | $0.00276 |
| Opus 5 | $0.00015 | $0.00138 |
| Sonnet 5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
haiku-zap 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 9d 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
Zap
Run a single task directly through a stage's hat loop — no intent file, no unit decomposition, no workflow tick. Stateless: nothing is written to .haiku/. Use it for bug fixes, typos, config tweaks, and small refactors where the cost of a mistake is "edit and re-run."
Call haiku_zap { task: "<the task>", studio?, stage? }.
studio/stageare optional. Omit them to default to the build-class execution stage of the software studio.- If the tool returns
zap_studio_not_foundorzap_stage_not_found, surface thevalid_studios/valid_stageslist withAskUserQuestion, let the user pick, and callhaiku_zapagain with their choice. - Otherwise follow the returned
messageverbatim. It contains the resolved studio/stage, the ordered hat sequence with each hat's role, a ready-to-spawn subagent prompt per hat, and the full run/verify/commit procedure (preflight, sequential dispatch, PASS/FAIL parsing, retry cap, commit-only-on-PASS).
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.
- 9d ago First seen · 15 lines · 29 tokens per session scan A c2752d4b4649
haiku-zap is a skill published in the GitHub repository gigsmart/haiku-method (24 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 276 once invoked, about $0.0001 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
contradiction-analysis
A structured way to analyze difficult problems by identifying competing forces, finding the main conflict, and deciding which side or issue has the greatest effect.
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.
concentrate-forces
A decision-making method for situations where several tasks compete for limited time, attention, computing power, or budget.
practice-cognition
A method for testing ideas in practice, learning from the results, and improving the next attempt through repeated cycles.
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…