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 skills add Xiaowen-Jiang/agent-enterprise --skill technical_documentationgit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/technical_documentation)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/technical_documentation"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/technical_documentation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/technical_documentation"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/technical_documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.00355 |
| Opus 5.5 | $0.00007 | $0.00142 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
Technical Documentation 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 1mo 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.
What it actually says
Process
- Identify the audience — Developer? Operator? End user?
- Choose the document type:
- ADR (Architecture Decision Record): Record a significant design decision
- README section: Getting started, usage, configuration
- Architecture guide: System overview, component interactions
- API docs: Endpoint reference, authentication, examples
- Runbook: Operational procedures, troubleshooting steps
- Read existing docs — Understand what's already documented
- Write with structure — Headers, bullet points, code examples
- Review for completeness — Does it answer who, what, why, how?
Output Format
For ADRs:
# ADR-NNN: [Title]
**Date**: YYYY-MM-DD
**Status**: Proposed / Accepted / Deprecated
## Context
[What prompted this decision]
## Decision
[What we decided to do]
## Consequences
[What changes as a result — both positive and negative]
For README sections:
Use clear headers, code blocks for commands, and step-by-step instructions.
Guidelines
- Write for someone who has never seen this codebase
- Include concrete examples and code snippets
- Explain WHY, not just HOW
- Keep sentences short and direct
- Use consistent terminology throughout
- Include prerequisites and assumptions
- Add diagrams when describing architecture (describe in text/ASCII)
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.
- 1mo ago First seen · 53 lines · 17 tokens per session scan A 13e2bc025477
Technical Documentation is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 355 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
atlas-report
Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
atlas-map
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
atlas-adr
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
atlas-present
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
atlas-onboard
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".