Borrowing it
Nothing to install: this file belongs to ucb-bar/merlin. 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/ucb-bar/merlin/main/.claude/skills/docs-layout/SKILL.mdgit clone --depth 1 https://github.com/ucb-bar/merlinWrote 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/ucb-bar/merlin/docs-layout)<a href="https://agentmods.dev/skills/ucb-bar/merlin/docs-layout"><img src="https://agentmods.dev/badge/skills/ucb-bar/merlin/docs-layout/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/ucb-bar/merlin/docs-layout"><img src="https://agentmods.dev/badge/skills/ucb-bar/merlin/docs-layout.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.00088 | $0.00874 |
| Opus 5.5 | $0.00035 | $0.00350 |
| Sonnet 5.5 | $0.00018 | $0.00175 |
| Haiku 4.5 | $0.00009 | $0.00087 |
Grade A, and why
docs-layout 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 15d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation layout (MANDATORY convention)
Documentation splits into three surfaces. Put each thing in the right one:
| Surface | What | Where |
|---|---|---|
| Central docs | Durable reference/guides/design for the whole repo | docs/reference/ · docs/guides/ · docs/design/ |
| Per-directory | Local purpose/invariants of one dir/package | that dir's AGENT.md (package ones auto-generated) |
| Point-in-time reports | Results, findings, status, presentations | artifacts/ (NOT docs/) — see the artifact-layout skill |
docs/README.md is the generated hub — do not hand-edit it; run the generator.
The three doc kinds (subdir = kind)
docs/reference/— durable, code-derived facts (architecture, dialects, runtime, generatedcli.md/module_index.md/schemas.md).docs/guides/— task-oriented how-tos (getting_started, dse, kernel_mining, targetgen, …).docs/design/— rationale / design notes / methodology.
If it snapshots a run (numbers, a specific experiment's outcome, a presentation), it is a report
— it goes to the matching artifacts/ concern (kernel-mining/, compare/, presentation/, …),
kept tracked via an explicit .gitignore negation if it's hand-written. It does not go in docs/.
Front-matter (required on every durable doc)
---
title: <human title>
kind: reference | guide | design
status: current | draft | superseded
owner: <area, e.g. dse | kernels | targetgen | runtime | core>
last_verified: YYYY-MM-DD # a claim someone reconciled this doc vs the code that day
related: [<slug>, ...] # other doc stems → cross-links in the hub
code_refs: [<paths the doc describes>] # → powers the drift detector
---
slug = the file stem (e.g. architecture). related and code_refs are what make docs navigable
and self-freshening — fill them in.
After you touch docs — regenerate + check
.venv/bin/python build_tools/scripts/gen_docs_index.py # rebuild docs/README.md hub
.venv/bin/python build_tools/scripts/check_docs.py # cli/package/schema/index/paths/freshness
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.
- 15d ago First seen · 71 lines · 88 tokens per session scan A 53b5d0e4f054
docs-layout is a skill published in the GitHub repository ucb-bar/merlin (21 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 874 once invoked, about $0.0004 per session on Opus 5.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-10-14.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…