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 onatm/agent-skills --skill docs-architecturegit clone --depth 1 https://github.com/onatm/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/onatm/agent-skills/docs-architecture)<a href="https://agentmods.dev/skills/onatm/agent-skills/docs-architecture"><img src="https://agentmods.dev/badge/skills/onatm/agent-skills/docs-architecture.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.1 | $0.00053 | $0.00568 |
| Opus 5 | $0.00026 | $0.00284 |
| Sonnet 5 | $0.00011 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
docs-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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Architecture
Maintain architecture-level docs without drifting into component internals or feature copy. Keep root and domain architecture docs aligned with the current topology and the docs they index.
Resource Map
- Use
assets/doc-starters/architecture-doc.mdwhen creating or substantially rewritingdocs/ARCHITECTURE.mdor a domain architecture doc such asweb-architecture.md. - Read
references/architecture-example.mdwhen you need a worked example of the expected level of abstraction.
When to Use
- New system boundary, pipeline stage, deployment model, or ownership boundary
- Changes to shared patterns used across multiple services or features
- Updates to architecture index docs that link to
docs/designs/ordocs/features/ - Domain architecture docs describing reusable patterns, topology, or trust boundaries
Do Not Use
- Component or service implementation detail that belongs in
docs-components-design - Feature behavior, user flows, or product narrative that belongs in
docs-feature-design
Workflow
- Identify the target architecture doc and its scope.
- Root architecture doc for the whole system
- Domain architecture doc for a shared surface such as web, API, or data
- Update only architecture-level content.
- System or domain boundaries
- Shared principles and patterns
- Cross-component data or control flow
- Runtime, deployment, trust boundaries, and ownership
- Keep architecture docs as index docs.
- Link to related
docs/designs/anddocs/features/docs - Summarize shared behavior instead of duplicating component internals
- Verify truth-bearing details.
- Active components and boundaries match the current code
- Flows, contracts, and ownership are still accurate
- Security and operations notes reflect the live system
- Trim stale detail.
- Remove implementation walkthroughs that belong in component docs
- Remove feature-level behavior copy that belongs in feature docs
Writing Rules
- Focus on topology, boundaries, and shared patterns
- Explain why the system is shaped this way, not every internal step
- Prefer concise diagrams and links over long prose dumps
- Treat the doc as an index and coordination surface, not a full implementation manual
What ships with it
3 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.
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 · 66 lines · 53 tokens per session scan A 074ad6287b48
docs-architecture is a skill published in the GitHub repository onatm/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 568 once invoked, about $0.0003 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
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.