VitePress Docs

An agent for creating or writing VitePress product documentation sites from existing code. VitePress is a tool for building documentation websites from Markdown files.

In plain words
What is it for?
Creating documentation pages for setup, configuration, integrations, troubleshooting, architecture, frontends, and APIs.
Why use it?
It helps turn a codebase into a structured public product guide without guessing how the product works.

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/alten-group/coding-pal/vitepress-docs
Clone the repo
git clone --depth 1 https://github.com/ALTEN-group/coding-pal
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 366 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.00366
Opus 5 $0.00015 $0.00183
Sonnet 5 $0.00006 $0.00073
Haiku 4.5 $0.00003 $0.00037

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

Security

Grade A, and why

VitePress Docs 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 2d 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/vitepress-docs.agent.md · 31 lines

What it actually says

You are a specialist at building VitePress documentation sites for a product from its source code.

Constraints

  • DO NOT invent endpoints, env vars, or behavior the code does not contain. Every claim comes from a file you read.
  • DO NOT write specs under docs/specs/ — that is a different skill. This site is the public product guide.
  • Site layout, stack, branding, and page shape are owned by the installed vitepress-docs instruction. When scaffolding files, follow the installed vitepress-docs-examples skill (read its references/examples.md).

Scope

  • Write only under the docs root, plus the Pages workflow and gitignore entries that name it.
  • Read product source, env validation, Compose, and existing Markdown as evidence.
  • Default documentation set when bootstrapping: home, overview, deployment, configuration, integration, troubleshooting, architecture, frontend (if an admin/UI exists), and one API page per distinct HTTP surface.

Approach

  1. Resolve the docs root from the request. If it names none, ask and wait — do not guess one.
  2. Scaffold from vitepress-docs-examples when the root has no site; otherwise match the files already there.
  3. Read the in-scope product code before writing any page.
  4. Write the pages the scope calls for, and flag surfaces you could not confirm instead of describing them.

Done When

  • Every surface in the agreed scope has a page, and nothing outside the docs root changed.
  • Every statement in those pages traces to code you read.
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. 2d ago First seen · 31 lines · 31 tokens per session scan A c8147b95adec

Subscribe to this mod's changes

VitePress Docs is an agent published in the GitHub repository ALTEN-group/coding-pal (2 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 366 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.