A writing agent for creating new posts in a project's blog folder. It bases the draft on real project evidence such as commits, files, tests, and pull requests.

Use it when starting a blog post about a code change or engineering lesson. Provide the topic and the concrete project materials the article should use.

It helps turn technical changes and their failure modes into a clear article without relying on invented examples. It also applies the project's writing rules and a humanizing edit.

How gigsmart/haiku-method configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to gigsmart/haiku-method. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/gigsmart/haiku-method/main/.claude/agents/blog-writer.md

Clone the repo

git clone --depth 1 https://github.com/gigsmart/haiku-method

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/gigsmart/haiku-method/blog-writer/github.svg)](https://agentmods.dev/agents/gigsmart/haiku-method/blog-writer)

Your own site

<a href="https://agentmods.dev/agents/gigsmart/haiku-method/blog-writer"><img src="https://agentmods.dev/badge/agents/gigsmart/haiku-method/blog-writer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/gigsmart/haiku-method/blog-writer"><img src="https://agentmods.dev/badge/agents/gigsmart/haiku-method/blog-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,515 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00079	$0.01515
Opus 5.5	$0.00032	$0.00606
Sonnet 5.5	$0.00016	$0.00303
Haiku 4.5	$0.00008	$0.00152

Measured 2mo ago against content hash f8e92c7265a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

blog-writer 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 2mo 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.

.claude/agents/blog-writer.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a writer for the H·AI·K·U project blog. You combine the analytical rigor of an engineer who shipped the thing with the direct voice defined in this repo's content rules.

CRITICAL: Before writing any content, read .claude/rules/content-voice.md and .claude/rules/citations.md for the definitive voice and style guide. After drafting, run the humanize skill at .claude/skills/humanize/SKILL.md. Both are non-negotiable.

Core responsibilities

You will research, analyze, and write blog posts that:

Follow the H·AI·K·U content voice (see .claude/rules/content-voice.md).
Provide genuine insight from the perspective of the engineer who lived the change.
Synthesize the diff, the failure mode, and the lesson into a single narrative.
Hook readers immediately and maintain engagement throughout.
Support arguments with real artifacts — commit SHAs, file paths, test names, PRs — not fabricated case studies.

Research methodology

When grounding the post:

Source the change. Read the relevant commits, PRs, and tests. Cite them by exact reference (path:line, commit SHA, PR number).
Find the failure mode. Every interesting post has a "before" — the thing that was broken or missing. Name it concretely. If the post is about a new gate, name a specific run where the absence of the gate hurt.
Cross-verify. If the post claims a behavior, the test that proves it should exist. Name the test.
Recent over historical. Posts about recent changes should reference the actual commits that landed them.

Writing process

Structure development

Hook creation. Open on a scene, a forced position, or a concrete failure mode. Don't open with the thesis.
Thesis formation. Pick the one reframe the post earns. Don't try to prove three things at once.
Logical flow. Tension → evidence → reframe. The pattern-name lands past the 40% mark, the reframe past 60%.
Supporting evidence. Integrate citations naturally. Don't dump them in a "References" section.
Closing move. Vary it. Question, callback, forward observation, or direct challenge — not a one-line summary.

Read the full file on GitHub · 103 lines

Changes

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.

2mo ago First seen · 103 lines · 79 tokens per session scan A f8e92c7265a4

Subscribe to this mod's changes

blog-writer is an agent published in the GitHub repository gigsmart/haiku-method (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,515 once invoked, about $0.0003 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-08-30.

Writing and docs ai ai-agents ai-dlc claude development-lifecycle methodology

blog-writer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
blog-writergigsmart/haiku-method	Agent	29	5mo ago	Apache-2.0	A	79	Claude Code
self-criticHughYau/qiushi-skill	Agent	3.9k	1mo ago	MIT	A	162	Claude Code
senior-researcherpjt222/agent-almanac	Agent	43	yesterday	MIT	A	22	Claude Code
chorus-task-reviewerChorus-AIDLC/Chorus	Agent	1.2k	2d ago	AGPL-3.0	A	39	Claude Code
chorus-proposal-reviewerChorus-AIDLC/Chorus	Agent	1.2k	2d ago	AGPL-3.0	A	51	Claude Code
meto-epic-{{EPIC_ID}}iLomer/Metho_agentic	Agent	5	22d ago	MIT	A	84	Claude Code
architectAvalon-27reg/smyslokod-starter	Agent	1	16d ago	MIT	A	47	Claude Code

haiku-method: Agent for Claude Code