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 agentmods add commands/aneja5/forge-skills/docsgit clone --depth 1 https://github.com/aneja5/forge-skillsWhat 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 | $0.00013 | $0.00189 |
| Opus 5 | $0.00006 | $0.00095 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
docs 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 2d 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.
What it actually says
Invoke the forge-skills:documentation-hygiene skill.
Define the README standard for every repo top-level (what this is, status, quick start, where things live, contributing, license) and every subdirectory with 5+ files. Set in-code comment policy — explain WHY, not WHAT. Comments required for non-obvious algorithm choices, workarounds, cross-file invariants, perf decisions. Forbidden for restating code or commented-out code. Establish doc-rot prevention — every doc has last-updated date, owner, and code permalinks. Prefer generated docs for API reference; hand-written docs for concepts and ADRs. Set changelog discipline — Keep-a-Changelog format, entry per user-visible change, updated in the PR not at release time.
After writing: "Docs policy written to .forge/docs-policy.md."
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.
- 2d ago First seen · 13 lines · 13 tokens per session scan A 174cbf0b758e
docs is a command published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 189 once invoked, about $0.0001 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 commands, from other repositories
index
Command "index" from cesarandreslopez/tauri-agent-tools, covering command reference, command summary, categories, visual capture and dom inspection.
console-monitor
Monitor console output (log/warn/error/info/debug) in real-time.
eval
Evaluate a JavaScript expression in the Tauri app's webview.
info
Show window geometry and display server info.
list-windows
List all visible windows, marking Tauri apps.
git
Unified git operations - commits, pull requests, and issue management.