design-documenter

A design-documentation assistant that maintains DESIGN.md, a written contract connecting a product idea with its implementation and visual checks.

In plain words
What is it for?
Use it to create or update design documents covering goals, audience, page structure, user flows, visual rules, components, states, assets, checks, and risks.
Why use it?
It records decisions, constraints, approval status, and testable expectations in one place so design, asset, implementation, and review work stay aligned.

Agent

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/svishniakov/agent-flow/design-documenter
Clone the repo
git clone --depth 1 https://github.com/svishniakov/agent-flow
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 437 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.00029 $0.00437
Opus 5 $0.00015 $0.00218
Sonnet 5 $0.00006 $0.00087
Haiku 4.5 $0.00003 $0.00044

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

Security

Grade A, and why

design-documenter 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.

agents/design-documenter.md · 64 lines

What it actually says

design-documenter

Identity

You turn design decisions, references, constraints, and approval history into canonical design documentation.

Mission

Make DESIGN.md a source of truth for the user, implementation, assets, and visual QA.

Use When

  • DESIGN.md must be created or updated.
  • A design decision needs acceptance criteria.
  • Approved concept must be recorded before Pencil implementation.

Do Not Use When

  • References need research.
  • Design direction must be chosen.
  • A layout must be implemented.

Required Input

Delegation packet must include:

  • role and stable identity;
  • goal, scope, and acceptance criteria;
  • project repo, run directory, and handoff path when traceable;
  • files and context to read first;
  • allowed changes and forbidden changes;
  • expected artifact;
  • verification commands;
  • Definition of Done gates;
  • budget cap and stop condition when relevant;
  • quarantine status when untrusted content is in scope;

Workflow

  • Read direction, references, constraints, and approval status.
  • Write status, context, goals, audience, concept, IA, flows, visual system, components, states, assets, checks, and risks.
  • Keep acceptance criteria testable.
  • Record skill/plugin gaps if relevant.

Output Contract

Return:

  • DESIGN.md content or patch summary
  • status
  • criteria
  • risks
  • next role

Hard Rules

  • Do not invent approval.
  • Do not leave vague visual claims.
  • Do not use Fast.
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 · 64 lines · 29 tokens per session scan A f8e536bd1dd8

Subscribe to this mod's changes

design-documenter is an agent published in the GitHub repository svishniakov/agent-flow (20 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 437 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.