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.
npx agentmods add skills/harnessprotocol/harness-kit/docgennpx skills add harnessprotocol/harness-kit --skill docgengit clone --depth 1 https://github.com/harnessprotocol/harness-kitWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00080 | $0.01753 |
| Opus 5 | $0.00040 | $0.00877 |
| Sonnet 5 | $0.00016 | $0.00351 |
| Haiku 4.5 | $0.00008 | $0.00175 |
Grade A, and why
docgen 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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generator
Overview
Generate or update project documentation from the codebase — READMEs, API references, architecture overviews, and changelogs. Designed to produce accurate, non-padded docs that match the project's existing style.
Core principles:
- Generate to conversation first. Never write a file without asking. Always: "Want me to write this to [path]?"
- Preserve manual content. If a doc already exists, identify what's outdated vs. what to keep. Don't blow away prose that was written by hand.
- Detect existing style. Match the formatting, heading levels, and tone of existing docs in the project.
- No filler. Omit empty or generic sections rather than padding them with boilerplate.
Invocation Examples
/docgen readme # generate or update project README
/docgen readme src/auth/ # README for a subdirectory or package
/docgen api src/routes/ # API endpoint documentation
/docgen architecture # architecture overview from codebase structure
/docgen changelog v0.2.0..v0.3.0 # changelog from git history for a version range
Workflow Order (MANDATORY)
You MUST follow this order. No skipping steps.
Step 1: Parse Input
Determine doc type and scope:
| Doc Type | Detection | Scope Default |
|---|---|---|
readme |
First arg is "readme" | Project root or specified path |
api |
First arg is "api" | Specified path (required); error if missing |
architecture |
First arg is "architecture" | Project root |
changelog |
First arg is "changelog" | Optional git range (e.g. v0.2.0..v0.3.0); defaults to recent history |
If no argument or unrecognized type: say "Usage: /docgen readme, /docgen api src/routes/, /docgen architecture, /docgen changelog [range]." Then stop.
If api is invoked without a path: say "Please provide a path. Example: /docgen api src/routes/." Then stop.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 216 lines · 80 tokens per session scan A fe655d33172d
docgen is a skill published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,753 once invoked, about $0.0004 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.
Other skills, from other repositories
learn
Guided, hands-on course teaching architects how to use Codex or Claude Code — six short modules, each built around an exercise on a bundled sandbox project (a fictional Brooklyn art museum expansion). Resumable across sessions via PROGRESS.md. Use when the user runs $learn or /as:learn, says they're new to AI-assisted…
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
epd-to-spec
Write CSI specification language for EPD submittals and sourced GWP limits. Use to add embodied-carbon or EPD requirements to specs; not to parse, find, or compare EPDs.
occupancy-calculator
Calculate code occupant loads by area with gross/net factors and jurisdiction checks. Use for "how many people can this space hold," IBC Table 1004.5, egress inputs, or occupancy-load reports; not for workplace headcount planning.
zoning-analysis-nyc
Analyze NYC lot zoning, FAR, height, setbacks, uses, and buildable envelope from PLUTO and the Zoning Resolution. Use for "what can I build"; use nyc-bsa for relief and zoning-envelope for 3D visualization.
workplace-programmer
Build office space programs through guided workplace strategy: area splits, room schedules, and planned seat counts. Use to program or size a workplace; not for code occupant-load calculations.