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 Emasoft/ai-maestro-architect-agent --skill amaa-documentation-writinggit clone --depth 1 https://github.com/Emasoft/ai-maestro-architect-agentWrote 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/emasoft/ai-maestro-architect-agent/amaa-documentation-writing)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-documentation-writing"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-documentation-writing/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/emasoft/ai-maestro-architect-agent/amaa-documentation-writing"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-documentation-writing.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.00040 | $0.00906 |
| Opus 5 | $0.00020 | $0.00453 |
| Sonnet 5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
amaa-documentation-writing 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 12d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer Skill
Overview
Technical documentation creation for module specs, API contracts, ADRs, and feature specs. DOCUMENTATION ONLY -- never write source code.
Checklist
Copy this checklist and track your progress:
- Receive and parse documentation assignment
- Gather context from existing code and specifications
- Select appropriate template from templates-reference.md
- Write core content following quality standards
- Add cross-references to related documents
- Perform 6 C's quality check (Complete, Correct, Clear, Consistent, Current, Connected)
- Commit document and report completion
Prerequisites
- Access to output directories (
/docs/module-specs/,/docs/api-contracts/,/docs/adrs/) - Read access to source code for reference
Instructions
- Receive and parse documentation assignment
- Gather context from existing code and specifications
- Create document structure using appropriate template from templates-reference.md
- Write core content following quality-standards.md
- Add cross-references to related documents
- Perform quality check against 6 C's (Complete, Correct, Clear, Consistent, Current, Connected)
- Commit document and report completion
Reference Documents
| Document | Content |
|---|---|
| templates-reference.md | Module Specification Template, Purpose, Responsibilities, Public Interface, Error Handling, Examples, Input Format Examples |
| quality-standards.md | Documentation Quality Criteria, Feature Specification Example, Executive Summary, User Stories, Functional Requirements, Non-Functional Requirements, Data Model |
| writing-workflow.md | Step 1: Receive and Parse Assignment, Step 2: Gather Context, Step 3: Create Document Structure, Step 4: Write Core Content, Step 5: Add Cross-References, Step 6: Quality Check, Step 7: Commit and Report |
| operational-guidelines.md | When to Create New Documents, When to Update Existing Documents, Document Organization, Version Control, Troubleshooting |
| agent-interactions.md | Upstream Agents (Receive Input From), Downstream Agents (Provide Output To), Peer Agents (Bidirectional), Handoff Protocol |
| op-write-module-spec.md | Purpose, When to Use, Inputs, Procedure, Usage Examples, Error Handling |
What ships with it
12 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.
- README.md 1.7 KB
- references/agent-interactions.md 3.8 KB
- references/op-quality-check-6c.md 5.6 KB
- references/op-write-adr.md 5.0 KB
- references/op-write-api-contract.md 5.6 KB
- references/op-write-feature-spec.md 5.2 KB
- references/op-write-module-spec.md 4.4 KB
- references/op-write-process-doc.md 4.7 KB
- references/operational-guidelines.md 3.7 KB
- references/quality-standards.md 6.0 KB
- references/templates-reference.md 3.7 KB
- references/writing-workflow.md 3.8 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.
- 12d ago First seen · 89 lines · 40 tokens per session scan A 164f51874fcd
amaa-documentation-writing is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 13d ago), licensed MIT. It adds 40 tokens to every session and 906 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…