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 mamahoos/dot-files --skill documentation-and-adrsgit clone --depth 1 https://github.com/mamahoos/dot-filesWrote 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/mamahoos/dot-files/documentation-and-adrs)<a href="https://agentmods.dev/skills/mamahoos/dot-files/documentation-and-adrs"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/documentation-and-adrs/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/mamahoos/dot-files/documentation-and-adrs"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/documentation-and-adrs.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.00058 | $0.02356 |
| Opus 5.5 | $0.00023 | $0.00942 |
| Sonnet 5.5 | $0.00012 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00236 |
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 17d 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.
This is a copy
97% identical to documentation-and-adrs — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation and ADRs
Overview
Document decisions, not just code. The most valuable documentation captures the why — the context, constraints, and trade-offs that led to a decision. Code shows what was built; documentation explains why it was built this way and what alternatives were considered. This context is essential for future humans and agents working in the codebase.
When to Use
- Making a significant architectural decision
- Choosing between competing approaches
- Adding or changing a public API
- Shipping a feature that changes user-facing behavior
- Onboarding new team members (or agents) to the project
- When you find yourself explaining the same thing repeatedly
When NOT to use: Don't document obvious code. Don't add comments that restate what the code already says. Don't write docs for throwaway prototypes.
Architecture Decision Records (ADRs)
ADRs capture the reasoning behind significant technical decisions. They're the highest-value documentation you can write.
When to Write an ADR
- Choosing a framework, library, or major dependency
- Designing a data model or database schema
- Selecting an authentication strategy
- Deciding on an API architecture (REST vs. GraphQL vs. tRPC)
- Choosing between build tools, hosting platforms, or infrastructure
- Any decision that would be expensive to reverse
Match the existing convention first
Before creating an ADR, inspect the available repository context for an established convention — existing ADRs, project instructions, and ADR-related configuration or tooling (e.g. an .adr-dir file). An established convention overrides the defaults below. Match:
- Location and format — e.g.
docs/adr/*.md,Documentation/Decisions/*.rst, a MADR layout, or anadr-toolssetup. Match the existing directory, file extension, and markup (Markdown vs reStructuredText). - Numbering and naming — continue the existing sequence and filename pattern (
ADR-004-Title.rst,0004-title.md, …); don't restart at 001 or introduce a second scheme. - Section headings — reuse the project's heading set rather than imposing this template's.
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.
- 17d ago Changed · +9 lines 516d4b33eff5
- 24d ago Changed eb2a10673da4
- 1mo ago Changed · +15 tokens per session fec867ef3cb1
- 1mo ago First seen · 290 lines · 43 tokens per session scan A 81a4314bb1e8
documentation-and-adrs is a skill published in the GitHub repository mamahoos/dot-files (5 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 2,356 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to documentation-and-adrs, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
golang-style
Go conventions specific to this author. Use before writing or editing any Go (.go) file.
gh-cli
GitHub CLI (gh) conventions and the inline PR review recipe. Use when working with GitHub repositories, PRs, issues, actions, gh api, or any GitHub operations from the command line.
gh-pr
This skill should be used when creating a GitHub pull request via gh pr create. Covers the gh CLI mechanics; PR title and body conventions come from the pr-style skill.
plan-loop
Plan work with the user in a PLAN.md, then implement it step by step, with /clear once the context fills up. Use before creating a plan, when the user mentions a PLAN.md, or when resuming work after /clear.
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
astro-dso-doc
Bootstraps a deep-sky object (DSO) astrophotography project from raw acquisition frames (own rig, not a smart telescope), AND generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), and a ready-to-paste PixInsight project Description…