generating-project-docs

A documentation workflow for creating or updating project files such as README.md, ARCHITECTURE.md, and STRUCTURE.md from the current codebase.

In plain words
What is it for?
Use it to refresh a project README, document system architecture or folder structure, or update one named documentation section.
Why use it?
It reduces stale or generic documentation by requiring descriptions to match files and commands that actually exist.

Skill for Claude CodeCodex

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 skills/marcusrbrown/systematic/generating-project-docs
Any agent
npx skills add marcusrbrown/systematic --skill generating-project-docs
Clone the repo
git clone --depth 1 https://github.com/marcusrbrown/systematic

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,391 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.00035 $0.02391
Opus 5 $0.00017 $0.01196
Sonnet 5 $0.00007 $0.00478
Haiku 4.5 $0.00003 $0.00239

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

Security

Grade A, and why

generating-project-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/skills/generating-project-docs/SKILL.md · 173 lines

How it starts

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

Generating Project Documentation

Overview

This plugin's documentation describes a live system whose surface (skills, agents, config schema, CLI) keeps changing. Generated docs go stale fast.

Core principle: Derive every fact from the live repository. Preserve the existing document's evolved structure. Never regress to a generic template.

If you cannot point at a file or command that justifies a sentence, do not write it.

When to Use

  • Refreshing README.md after new skills, agents, or features land
  • Fixing documentation drift (counts, structure, CLI output, runtime claims)
  • Updating ARCHITECTURE.md or STRUCTURE.md when the codebase layout changes
  • Adding or refreshing a scoped section (e.g. only the "Quick Install" block)

When NOT to Use

  • Writing planning docs (docs/plans/, docs/brainstorms/) — those follow their own templates
  • Authoring skill or agent files — those have their own format rules

Arguments

$ARGUMENTS
  • Empty or readme — Update README.md (default)
  • architecture — Update ARCHITECTURE.md
  • structure — Update STRUCTURE.md
  • all — Update all three docs
  • <section-name> — Update only that named section within the target doc (e.g. skills, agents, cli)

For scoped updates: read the current document, locate the section by heading, replace only that section's content. Preserve surrounding structure exactly.

Pre-Generation Inventory

Before writing anything, gather these from the live repo:

Source What to extract
package.json name, version, description, scripts, repository URL
bun src/cli.ts list skills 2>/dev/null exact skill count and names
bun src/cli.ts list agents 2>/dev/null exact agent count, names, categories
bun src/cli.ts list commands 2>/dev/null command inventory
find skills -name SKILL.md -exec head -6 {} \; -exec echo --- \; skill frontmatter (name, description)
find agents -maxdepth 2 -name '*.md' -exec head -4 {} \; -exec echo --- \; agent frontmatter (name, description), category from path
Current target doc existing structure, badges, nav links, voice
git log --oneline -15 recent change context

Read the full file on GitHub · 173 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. 2d ago First seen · 173 lines · 35 tokens per session scan A 26c216d07df1

Subscribe to this mod's changes

generating-project-docs is a skill published in the GitHub repository marcusrbrown/systematic (24 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 2,391 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-30.