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 thiientv/godmode --skill documentation-and-adrsgit clone --depth 1 https://github.com/thiientv/godmodeWrote 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/thiientv/godmode/documentation-and-adrs)<a href="https://agentmods.dev/skills/thiientv/godmode/documentation-and-adrs"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/documentation-and-adrs.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.00335 |
| Opus 5 | $0.00031 | $0.00168 |
| Sonnet 5 | $0.00012 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
documentation-and-adrs 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.
What it actually says
Documentation and ADRs
Document the decision a future maintainer needs, not the whole conversation.
Documentation workflow
- Identify the reader, decision or task, freshness owner, and expected action.
- Inspect the source of truth, commands, configuration, and current behavior.
- Separate facts, assumptions, examples, and recommendations. Mark version or environment-specific statements.
- Put the shortest usable path first; move exhaustive details to a linked reference.
- Test every command, code sample, relative link, and stated file path that the environment permits.
ADR workflow
Use an ADR when a choice affects interfaces, architecture, data, operations, security, or future contributors. Record context, decision, alternatives, consequences, rejected options, migration/rollback, and status. Do not use an ADR to hide an unresolved decision; mark it proposed or superseded honestly.
Read adr-template.md. Keep README content as a front door and link to deeper docs; avoid stale feature walls and hardcoded claims that the repository cannot verify.
Completion condition
The intended reader can act from the document, links and examples resolve, and the document's factual or verification limits are visible.
What ships with it
1 file 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 · 41 lines · 62 tokens per session scan A c36743a5c7eb
documentation-and-adrs is a skill published in the GitHub repository thiientv/godmode (94 stars, last pushed 12d ago), licensed MIT. It adds 62 tokens to every session and 335 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-30.
Other skills, from other repositories
agent-evaluation-v2
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation-v3
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.