Borrowing it
Nothing to install: this file belongs to briandconnelly/moonbridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/briandconnelly/moonbridge/main/.agents/skills/agent-friendly-docs/SKILL.mdgit clone --depth 1 https://github.com/briandconnelly/moonbridgeWrote 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/briandconnelly/moonbridge/agent-friendly-docs)<a href="https://agentmods.dev/skills/briandconnelly/moonbridge/agent-friendly-docs"><img src="https://agentmods.dev/badge/skills/briandconnelly/moonbridge/agent-friendly-docs.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.00169 | $0.01183 |
| Opus 5 | $0.00084 | $0.00592 |
| Sonnet 5 | $0.00034 | $0.00237 |
| Haiku 4.5 | $0.00017 | $0.00118 |
Grade A, and why
agent-friendly-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 6d 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
100% identical to agent-friendly-docs — 0 lines 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Friendly Docs
Use this skill to make a repo's documentation surface cheap for agents to navigate and trust.
Core Standard
- Structure docs by layer and route by task: an agent reaches the doc that answers its question without reading everything.
- Give every fact exactly one authoritative home; everything else links to it.
- Label historical material (ADRs, postmortems) as historical, not current policy.
- Spend agent tokens deliberately: keep the instruction layer minimal and always-loaded; put heavier material behind explicit pointers.
- Treat freshness as a mechanism, not an intention: ownership, PR doc-update expectations, generated-doc provenance, and verifiable links and commands.
- Make every embedded command or example runnable as written from the repo root, or state its preconditions.
When To Use
- Designing or restructuring a repo's documentation surface.
- Auditing an existing documentation surface for agent-friendliness.
- Diagnosing a concrete agent failure: missing project conventions, reading stale docs, re-deriving context every session.
When Not To Use
- Published documentation sites or llms.txt — this skill covers repo-internal docs only.
- Generic prose quality or writing style with no agent-consumption angle.
- Instruction-file strategy and repo safety configuration — use agent-friendly-github.
- Rules-vs-context content audits of instruction-file prose — use separating-context-from-constraints.
- Trivial edits to a doc surface that is already well-layered; just make the edit.
Vocabulary
- Instruction layer — always-loaded binding norms: the canonical instruction file plus thin per-harness adapters. Adapter strategy itself is owned by agent-friendly-github, not this skill.
- Orientation layer — read-on-demand maps: README, architecture overviews, CONTEXT.md, per-directory context files. Loaded when an agent orients itself, not on every turn.
- Reference layer — detailed how-to and API material, loaded only when a task demands it. Kept out of the instruction layer precisely because it is heavy.
- Decision history — ADRs and postmortems that explain why a past choice was made. Never binds unless promoted into a current-policy doc.
- Code-adjacent context — comments and docstrings carrying constraints that must travel with the code. Repo-wide context does not belong here even when it is convenient to write.
- Canonical instruction file — the one instruction file a harness reads directly. Other harnesses point at it through a thin adapter instead of duplicating it.
- Per-harness adapter — a thin, harness-specific file that points at the canonical instruction file instead of restating it.
- Read path — the sequence of docs an agent loads, in order, to complete a given task.
- Authoritative vs historical — whether a doc states current policy or merely records a past decision.
- Generated-doc provenance — a marker on a generated file naming its source and regeneration command.
- These layers are a routing lens for "what does an agent read first, what is authoritative, what is historical, what is ignorable" — not a filing system every repo must adopt.
What ships with it
5 files 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.
- 6d ago First seen · 75 lines · 169 tokens per session scan A 3aa521aa2097
agent-friendly-docs is a skill published in the GitHub repository briandconnelly/moonbridge (0 stars, last pushed 4d ago), licensed MIT. It adds 169 tokens to every session and 1,183 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-friendly-docs, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
novel-game-analyze
Deconstruct a novel for game adaptation. Compress a raw novel, deconstruction library, or writing project into a SOURCEBIBLE with cited textual evidence, extracting world rules, player verbs, spaces, character will, systems, and visual anchors — without inventing a genre yet. Use for gameable book analysis, analyze a…
novel-to-game
Turn a novel into a fully playable game on the selected target platform. Orchestrates the whole adaptation pipeline — requirements intake, gameable deconstruction, concept selection, world and visual design, target-runtime build, and evidence-based QA — for a novel in any language. Use for novel to game, story to…
writing-release-notes
Use when preparing, refreshing, backfilling, or redrafting a release-notes page under docs/releases/ before opening a normal review pull request.
skills
Generate a complete SVG file from a natural language description using SEP-1577 multi-step sampling.
pr-alignment-loop
Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…
vault-workflow
Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.