Borrowing it
Nothing to install: this file belongs to indianic/byline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/indianic/byline/main/.claude/commands/write-series.mdgit clone --depth 1 https://github.com/indianic/bylineWrote 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/commands/indianic/byline/write-series)<a href="https://agentmods.dev/commands/indianic/byline/write-series"><img src="https://agentmods.dev/badge/commands/indianic/byline/write-series/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/commands/indianic/byline/write-series"><img src="https://agentmods.dev/badge/commands/indianic/byline/write-series.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.00024 | $0.02045 |
| Opus 5.5 | $0.00010 | $0.00818 |
| Sonnet 5.5 | $0.00005 | $0.00409 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
write-series 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write and publish through Byline. Arguments: $ARGUMENTS
Without --count (or with --count 1), write and publish ONE article on the given
topic — skip straight to Per-article steps below and run it once.
With --count N (N from 2 to 12), the argument after site/persona is a THEME, not a
single topic: plan a pillar-and-spokes series of N articles on that theme, get the
user's approval on the titles, then run Per-article steps once per article.
Step 0 — Plan the series (only when --count > 1)
Call plan_series with the persona, the theme, count, and the target site. It
returns a brief (prose instructing you how to propose titles), a series_id, and
one seed per slot — each slot already carries a distinct hook, arc, texture and
author presence, so the titles you propose do not need to worry about sounding alike.
Planning never fails: if the series runs longer than one of those dimensions has
options, some slot is forced to repeat it, and that slot's repeats array names
which dimension — check it, and vary that slot's title angle a little harder by hand
if it's non-empty.
Follow the returned brief exactly: propose article 1 as the pillar (the theme's head
question, for a reader who knows nothing) and every later slot as a spoke (one
long-tail question, answered in depth, linking back to the pillar once). Give each
title its primary keyword and the question it answers. Then stop and show the list
to the user before writing anything else. Byline does not invent the titles —
you do, from the brief — and nothing gets written until the user approves the list
or asks for changes.
Once approved, run Per-article steps once per slot, in order, passing that slot's
seed as build_writing_brief's seed, plan_series's series_id as series
throughout, and that slot's approved title/keyword/question as the topic for step 1.
Per-article steps
The point of this command is that a correct article costs six tool calls, not the eighteen a series run used to take. Do not add calls the steps below do not ask for.
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 · +70 lines 57369673e975
- 2mo ago First seen · 89 lines · 24 tokens per session scan A fc0d2b2a88bc
write-series is a command published in the GitHub repository indianic/byline (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 2,045 once invoked, about $0.0001 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-31.
write-series compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| write-seriesindianic/byline | Command | 2 | 1mo ago | MIT | A | 24 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| convergegithub/spec-kit | Command | 148k | today | MIT | A | 35 | Claude Code |
| speckit.bug.testgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | today | MIT | A | 26 | Claude Code |