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-update-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-update-document)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-document"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-document/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/andrevianna/aid-methodology/aid-update-document"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-document.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.00137 | $0.01170 |
| Opus 5 | $0.00068 | $0.00585 |
| Sonnet 5 | $0.00027 | $0.00234 |
| Haiku 4.5 | $0.00014 | $0.00117 |
Grade A, and why
aid-update-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 9d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Document (update it now, resolve nothing)
/aid-update-document updates an existing document -- the sibling of
/aid-create-document for edits rather than new authoring.
Same collapse shape, same producer/verifier, same KB boundary; the difference
is it locates and reads the existing document first, edits it, and shows a diff at
the human gate (overwrite care is central).
- Boundary vs the KB: never writes
.aid/knowledge/; KB edits route to/aid-update-kb. - Not a numbered pipeline phase; does not route to
/aid-execute. - Genre structures:
.claude/aid/templates/shortcut-scaffolding/document.md.
State machine: INTAKE -> AUTHOR -> VERIFY (loop) -> PRESENT [human gate, diff] -> WRITE
(on approval) -> DONE. Print the [State: NAME] -- {purpose} entry line on each state.
State: INTAKE
- Require a target document + a change. Empty argument -> ask one bootstrapping question ("Which document should I update, and what change?") and wait.
- Locate + read the existing document. If it cannot be resolved, ask (or, if the user
meant a new doc, suggest
/aid-create-document). - Pick the path (fast if the document + change are clear; guided otherwise) and
classify complexity ->
aid-tech-writermodel/effort (sonnet/medium default; opus/high for a large rewrite). 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 (initiator: aid-update-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.
- 9d ago First seen · 109 lines · 137 tokens per session scan A 65a736a27d31
aid-update-document is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 137 tokens to every session and 1,170 once invoked, about $0.0007 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-09-03.
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…