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 yuusakuri/agent-skills --skill document-architecturegit clone --depth 1 https://github.com/yuusakuri/agent-skillsWrote 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/yuusakuri/agent-skills/document-architecture)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/document-architecture"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/document-architecture/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/yuusakuri/agent-skills/document-architecture"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/document-architecture.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.00091 | $0.01136 |
| Opus 5 | $0.00046 | $0.00568 |
| Sonnet 5 | $0.00018 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
document-architecture 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Architecture
Create decision-ready system documents without duplicating the responsibility of PRDs, ADRs, technical exploration, or implementation plans.
Route the request
Select exactly one primary document type, then read its reference completely.
| Requested outcome | Read |
|---|---|
| Define business and system requirements, scope, and acceptance | references/requirements-definition.md |
| Record a selected technical approach for implementers | references/technical-spec.md |
| Define externally observable behavior and major internal boundaries | references/basic-design.md |
| Define implementation-level modules, processing, data updates, and unit tests | references/detailed-design.md |
| Propose a system investment, delivery, cost, and benefit to a customer | references/system-proposal.md |
| Propose business improvement or a new operating initiative | references/business-proposal.md |
Always read references/quality-checklist.md before finalizing the document. Do not read unrelated document references.
Preserve artifact ownership
- Use
deliver-prdfor a product requirements document covering the customer problem, value, product scope, and outcomes. - Use
brainstormingwhen a technical approach is unresolved. Compare options first, then record the selected approach in the technical document. - Use
spec-driven-developmentfor a coding implementation specification. - Use
planning-and-task-breakdownfor file-level implementation tasks and verification steps. - Use
documentation-and-adrsfor an architecture decision record explaining a costly-to-reverse decision. - Use
develop-solution-brieffor a short internal alignment document. - Use this skill for formal requirements, specifications, designs, and proposals after identifying their inputs and decision audience.
Update or reference an existing canonical artifact. Never create a second document that owns the same decision or requirement.
Follow the coauthoring workflow
What ships with it
9 files 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.
- agents/openai.yaml 318 B
- assets/templates/base-document.docx 39 KB
- references/basic-design.md 3.9 KB
- references/business-proposal.md 3.9 KB
- references/detailed-design.md 3.9 KB
- references/quality-checklist.md 3.5 KB
- references/requirements-definition.md 4.7 KB
- references/system-proposal.md 4.1 KB
- references/technical-spec.md 4.3 KB
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.
- 8d ago First seen · 96 lines · 91 tokens per session scan A ddea9e5b5350
document-architecture is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 1,136 once invoked, about $0.0005 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.