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/xiaowen-jiang/agent-enterprise/technical_documentationnpx 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.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00355 |
| Opus 5 | $0.00009 | $0.00178 |
| Sonnet 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 4d 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.
- 4d 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 5mo ago), licensed MIT. It adds 17 tokens to every session and 355 once invoked, about $0.0001 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.
Other skills, from other repositories
sync-confluence
Syncs engineering documentation (ADR, RFC, architecture) from docs/engineering/ to Confluence Cloud using the mark tool. Operates in two modes: scaffold (creates the directory tree locally) and CI sync (pushes on every main push). Only files with mark metadata headers are synced. Enforces diagram hierarchy (Mermaid >…
spec-authoring
Standard for authoring engineering behavior-contract specs in docs/specs/: scope subsystems, assign stable IDs, structure docs, manage lifecycle.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
ce-optimize
Run metric-driven optimization loops. Use when improving a measurable outcome through experiments.
golden-rss
Use when testing the rss golden build.