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 bestdeejay-design/agent-skills --skill docs-systemgit clone --depth 1 https://github.com/bestdeejay-design/agent-skillsWrote 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/bestdeejay-design/agent-skills/docs-system)<a href="https://agentmods.dev/skills/bestdeejay-design/agent-skills/docs-system"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/docs-system/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/bestdeejay-design/agent-skills/docs-system"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/docs-system.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.00122 | $0.00761 |
| Opus 5.5 | $0.00049 | $0.00304 |
| Sonnet 5.5 | $0.00024 | $0.00152 |
| Haiku 4.5 | $0.00012 | $0.00076 |
Grade A, and why
docs-system 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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs System — meta-guide & router
This skill is now the meta-guide. The two branches live in focused skills: load them directly. Use this skill for the big picture: which docs to write, in which order, and how complete the set must be.
Two branches of documentation
| Branch | Answers | Skill |
|---|---|---|
| Product docs — «why» and «what» | VISION → PRD → ROADMAP → FEATURES | docs-product |
| Project docs — «how» | README/ENTRY/ARCHITECTURE/ADR/contracts/tests + REFERENCE map | docs-project |
Rule: product docs answer «why» and «what»; engineering docs answer «how». If a doc has no reader and no question it answers — it does not belong.
When to use this skill (router)
- The task is about the documentation SYSTEM as a whole: what to write, in what order, how complete.
- The phases / levels / completeness gates need to be applied.
- The task is clearly product OR engineering → load the branch directly instead.
Order and levels
- Phase order (when to write each doc):
references/order.md. - Levels L1/L2/L3 (how deep a doc set must be for the system size):
references/levels.md. - Completeness checklist (what a complete doc set looks like):
references/completeness.md.
Golden rules
- Nothing is written "from the end": VISION → PRD → ROADMAP → FEATURES, then engineering docs.
- Contracts (OpenAPI/AsyncAPI) are written BEFORE code.
- The map (
REFERENCE.md) is written last — it describes everything above it. - Example monorepo that follows all rules:
examples/example-monorepo/. - Skill roadmap:
ROADMAP.md.
Removal plan
Keep as the meta-guide (not deprecated — it still carries order/levels/ completeness). The two branches are the focused entry points.
Boundaries
- Do not use to author one document branch directly; route to
docs-productordocs-project.
Evidence and completion gate
Ground recommendations in the supplied repository or brief. State assumptions, missing inputs, and unresolved risks. Return a concrete artifact or checklist with an owner/action for each open item, then verify that the result answers the requested goal rather than merely repeating the framework.
What ships with it
8 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.
- 1mo ago Changed · +8 lines b71deb3a681d
- 1mo ago First seen · 56 lines · 122 tokens per session scan A 7b0fe872962a
docs-system is a skill published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 761 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
composio
Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help…
refit
Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.