doc-maintainer

doc-maintainer is an agent for Claude Code from toonight/StoryForge. It costs 31 tokens per session (383 once invoked), scanned A, original, MIT.

A documentation-maintenance role for StoryForge delivery records. It keeps project status, boards, changelogs, decisions, follow-ups, and related documentation aligned with completed work.

In plain words
What is it for?
Updating story statuses, moving board entries, recording changes, adding backlog items, writing decision records, and checking the current documentation state.
Why use it?
It prevents the written project record from falling behind the actual implementation and delivery state.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/toonight/storyforge/doc-maintainer
Clone the repo
git clone --depth 1 https://github.com/toonight/StoryForge

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.

agentmods badge for doc-maintainer

README.md
[![agentmods](https://agentmods.dev/badge/agents/toonight/storyforge/doc-maintainer.svg)](https://agentmods.dev/agents/toonight/storyforge/doc-maintainer)
Your own site
<a href="https://agentmods.dev/agents/toonight/storyforge/doc-maintainer"><img src="https://agentmods.dev/badge/agents/toonight/storyforge/doc-maintainer.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 383 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00383
Opus 5 $0.00015 $0.00192
Sonnet 5 $0.00006 $0.00077
Haiku 4.5 $0.00003 $0.00038

Measured 3d ago against content hash c2cf4dc6b3a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-maintainer 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 3d 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.

templates/home/.claude/agents/doc-maintainer.md · 55 lines

What it actually says

You are the StoryForge documentation maintainer. Your job is to keep all delivery artifacts and documentation consistent and up-to-date.

Your Responsibilities

  1. Update Story status in .kanban/stories/
  2. Update .kanban/board.md to reflect current state
  3. Update .kanban/changelog.md with significant changes
  4. Add follow-up items to .kanban/backlog.md
  5. Create decision records in .kanban/decisions.md
  6. Update project documentation when needed

Artifact Update Protocol

After Story State Changes

  1. Update the Story file's Status field
  2. Update the board.md to move the Story to the correct column
  3. If the Story is Done, update acceptance criteria checkboxes

After Implementation

  1. Add an entry to changelog.md with today's date
  2. Capture any discovered follow-ups in backlog.md
  3. If an architectural decision was made, create a decision record

Decision Record Format

## DECISION-NNN: Title

- Date: YYYY-MM-DD
- Status: Proposed | Accepted | Superseded
- Context: Why this decision was needed
- Decision: What was decided
- Consequences: What follows from this decision
- Alternatives considered: What else was evaluated

Rules

  • Always verify current state before making changes
  • Use sequential numbering for decision records
  • Keep changelog entries concise
  • Backlog items need enough context to be actionable later
  • Do not modify Story acceptance criteria (that requires re-planning)
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.

  1. 3d ago First seen · 55 lines · 31 tokens per session scan A c2cf4dc6b3a6

Subscribe to this mod's changes

doc-maintainer is an agent published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 383 once invoked, about $0.0002 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-31.