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 AndreVianna/aid-methodology --skill aid-create-documentgit clone --depth 1 https://github.com/AndreVianna/aid-methodologyWrote 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/andrevianna/aid-methodology/aid-create-document)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-create-document"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-create-document.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.00199 | $0.01743 |
| Opus 5 | $0.00100 | $0.00872 |
| Sonnet 5 | $0.00040 | $0.00349 |
| Haiku 4.5 | $0.00020 | $0.00174 |
Grade A, and why
aid-create-document 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Document (write it now, resolve nothing)
/aid-create-document writes a document now and places it on your approval. It
determines the format (markdown, mermaid diagram, HTML, a table) and the structure
(ADR, runbook, tutorial, changelog, general/Diataxis, ...) from the request -- deferring to
intelligence, not a per-kind skill. The genre skills
(/aid-document-decision, -architecture, -guideline, -standard, -runbook,
-tutorial, -changelog) and /aid-create-diagram are thin kind-siblings that delegate
here binding a genre/format hint.
- Boundary vs the KB: this never writes
.aid/knowledge/. If the content belongs in the KB, print a handoff to/aid-update-kb. The KB isaid-discover/aid-update-kbterritory (its own authoring rules + grading). - Boundary vs
/aid-design:aid-designproduces a design (aid-architect);aid-create-documentwrites documentation about something (aid-tech-writer). - Not a numbered pipeline phase; does not route to
/aid-execute. - Genre structures (ADR / C4 / runbook / ...):
.claude/aid/templates/shortcut-scaffolding/document.md.
State machine: INTAKE -> AUTHOR -> VERIFY (loop) -> PRESENT [human gate] -> PLACE (on
approval) -> DONE. Print the [State: NAME] -- {purpose} entry line on each state.
State: INTAKE
- Require a subject. Empty argument -> ask one bootstrapping question ("What do you want documented, and for whom?") and wait.
- Resolve format + genre from the request (or the hint a kind-sibling bound): e.g. "an
ADR for X" -> markdown ADR; "a diagram of the pipeline" -> mermaid; "the release notes"
-> changelog. Use the genre structures in
document.md. - Pick the path: Fast -- a clear subject + kind -> author now. Guided -- vague -> scope subject / audience / kind first.
- Classify complexity (model + effort): most docs ->
aid-tech-writerat sonnet / medium; a heavy architecture write-up -> opus / high. Verifier tier >= producer. - Consult the Work Initiation Gate, then allocate the work folder + STATE. First run
the gate (
.claude/aid/templates/work-initiation-gate.md):bash .claude/aid/scripts/works/enumerate-works.sh(main tree + every git worktree). Empty -> allocate, no prompt. Works exist -> ask new-vs-continuation; on continuation route to the chosen work's resume door and STOP (allocate nothing); on new work: create and enter the worktree per the gate's§ 3astep 2 (worktree-lifecycle.sh create <work-id> <name>, STOP on a non-zero exit or empty path, else enter the resolved path), then allocate (pipeline.path: lite,initiator: aid-create-document,lifecycle: Running,active_skill: aid-create-document;phasenot driven). - Read the design seed, if present. If
.aid/design/document.mdexists, read it as prior context before drafting; it is an input, never a substitute, and is not modified by this run.
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 · 134 lines · 199 tokens per session scan A e7b4f3caebbf
aid-create-document is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 199 tokens to every session and 1,743 once invoked, about $0.0010 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.