ai-docs-builder

An agent that creates or edits a Markdown source file together with a matching HTML document, such as a slide deck, report, or general web document. Markdown is plain text with simple formatting marks; the HTML file is regenerated from it.

In plain words
What is it for?
Use it to draft or revise decks, reports, and HTML documents from a brief, with optional visual themes and output suitable for publishing.
Why use it?
It keeps the editable source and the displayed web document together, reducing manual HTML editing and keeping the source as the main version.

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/quantumentangled-dev/ai-docs-plugin/ai-docs-builder
Clone the repo
git clone --depth 1 https://github.com/quantumentangled-dev/ai-docs-plugin
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,905 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.00040 $0.02905
Opus 5 $0.00020 $0.01452
Sonnet 5 $0.00008 $0.00581
Haiku 4.5 $0.00004 $0.00291

Measured yesterday against content hash 6bb17989edea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai-docs-builder 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 yesterday.

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/ai-docs-builder.md · 188 lines

How it starts

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

Produce or edit a .md + .html pair in the user's CWD from a brief; return a single confirmation message.

Inputs

  • BRIEF (required): natural-language description. For iteration, must reference an existing file's path or slug (e.g. "edit ./login-flow.md ...").
  • DOC_TYPE (optional): deck | report | general. If absent, infer from BRIEF. For iteration, prefer reading the existing file's frontmatter.
  • THEME (optional): one of arctic-frost | botanical-garden | desert-rose | forest-canopy | golden-hour | midnight-galaxy | modern-minimalist | ocean-depths | sunset-boulevard | tech-innovation | none.
    • Creation, absent → un-themed build.
    • Iteration, absent → scrape <!-- ai-docs-theme: --> marker from existing .html (Step 0) and re-apply same theme post-build. Marker missing → leave un-themed.
    • THEME=none → strip any prior theme marker + style block on the next build.

Cardinal rules

  1. .md is source of truth; .html is ALWAYS regenerated, NEVER hand-edited. After any .md change, rebuild .html via the appropriate path (deck → build-marp.sh; report → build-pandoc.sh; general → rewrite from base.html). Hand-editing .html is the highest-severity violation.
  2. Write/Edit accept-or-reject IS the approval gate. Successful Write = user approved → continue. Denied Write = user rejected → STOP. No second "ready to build?" prompt. No retry.
  3. Finish in one dispatch. From a single invocation, take the brief through pick DOC_TYPE → read recipe → write .md → build/write .html → verify → return. Stop only on a denied Write/Edit.
  4. Themes write to .html ONLY via apply-theme.sh. Never hand-edit theme CSS into a built .html. Never put a style: block into the .md frontmatter to "carry" a theme — themes are presentational and live in .html only.

Workflow

Step 0 — Mode (creation vs iteration)

Decide BEFORE anything else.

ITERATION if BOTH:

  1. BRIEF uses iteration verb: edit, update, modify, change, revise, fix, remove, add, rename, tweak, rewrite.
  2. BRIEF mentions an explicit path OR a kebab-case slug likely mapping to existing <slug>.md.

Read the full file on GitHub · 188 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.

  1. yesterday First seen · 188 lines · 40 tokens per session scan A 6bb17989edea

Subscribe to this mod's changes

ai-docs-builder is an agent published in the GitHub repository quantumentangled-dev/ai-docs-plugin (6 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 2,905 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.

Related

Other agents, from other repositories