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 agentmods add skills/bestdeejay-design/agent-skills/docs-projectnpx skills add bestdeejay-design/agent-skills --skill docs-projectgit 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-project)<a href="https://agentmods.dev/skills/bestdeejay-design/agent-skills/docs-project"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/docs-project.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.00163 | $0.01427 |
| Opus 5 | $0.00081 | $0.00714 |
| Sonnet 5 | $0.00033 | $0.00285 |
| Haiku 4.5 | $0.00016 | $0.00143 |
Grade A, and why
docs-project 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Project — engineering documentation («how»)
Use this skill to write the engineering documents: architecture, decisions
(ADR), contracts, dev guides, tests, and the documentation map. Assumes the
product docs exist (docs-product: VISION/PRD/ROADMAP/FEATURES).
When to use
- A project needs its engineering docs: README, ENTRY, ARCHITECTURE, ADR, tests.
- User asks for "проектная документация", "архитектура документация", "adr", "инженерная документация", "контракты openapi", "engineering docs".
- Contracts (OpenAPI/AsyncAPI) must be written before code.
Do NOT use
- For product docs (VISION/PRD/ROADMAP/FEATURES) — that is
docs-product. - For the meta-guide (phases, levels L1/L2/L3, completeness checklist) —
docs-system.
Root documents
| File | Purpose | Phase | Template |
|---|---|---|---|
README.md |
Overview: what it is, stack, status, quick start, structure | 1 → 10 | templates/project/README.tmpl |
ENTRY.md |
Entry point: "start here", navigation "topic → file", onboarding checklist | 9 | templates/project/ENTRY.tmpl |
AGENT.md |
Runbook for the autonomous build agent: phases, rules, DoD, commit gate | 8 | — |
DELIVERY.md |
Delivery gate: build/run/verify, what's in, what's NOT | 8 | — |
| Legal/community | LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY | 1/9 | — |
docs/ — engineering documents
| File | Purpose | Phase | Template |
|---|---|---|---|
docs/REFERENCE.md |
The map. Card for EVERY doc: purpose/structure/facts/links, hierarchy of truth, drift table. Written last. | 10 | templates/project/REFERENCE.tmpl |
docs/ARCHITECTURE.md |
Components, communication, data flows, tech stack | 2 → 6 | templates/project/ARCHITECTURE.tmpl |
docs/ADR/ADR-000.md |
Architecture Decision Records — one per significant decision | 2 (ongoing) | templates/project/ADR-000.tmpl |
docs/SAGA.md |
Cross-module scenarios (choreography, events, compensation, idempotency) | 5 | templates/project/SAGA.tmpl |
docs/TEST_CASES.md |
Test cases (Gherkin-style) + coverage matrix | 6 | templates/project/TEST_CASES.tmpl |
docs/DEV_GUIDE.md |
Local dev: prerequisites, run, env, migrations, debugging | 7 | templates/project/DEV_GUIDE.tmpl |
docs/IMPROVEMENTS.md |
Known issues / doc-vs-fact drift + prioritized fix plan | 8 | templates/project/IMPROVEMENTS.tmpl |
docs/TROUBLESHOOTING.md |
Runtime error diagnostics (E1…En) + startup checklist | 8 | templates/project/TROUBLESHOOTING.tmpl |
docs/BACKLOG.md |
Ideas, deferred features, priorities | 1 | templates/project/BACKLOG.tmpl |
docs/REVIEW.md |
Doc audit: problems, resolutions, per-service status | 10 | templates/project/REVIEW.tmpl |
docs/STATUS.md |
L1 alternative to REVIEW: done / in progress / limitations | 10 | templates/project/STATUS.tmpl |
What ships with it
16 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.
- readme.ru.md 1.3 KB
- references/project-docs.md 4.5 KB
- skill.json 1.5 KB
- templates/project/ADR-000.tmpl 1.1 KB
- templates/project/ARCHITECTURE.tmpl 1.8 KB
- templates/project/BACKLOG.tmpl 1.2 KB
- templates/project/DEV_GUIDE.tmpl 1.9 KB
- templates/project/ENTRY.tmpl 3.4 KB
- templates/project/IMPROVEMENTS.tmpl 1.8 KB
- templates/project/README.tmpl 1.9 KB
- templates/project/REFERENCE.tmpl 4.4 KB
- templates/project/REVIEW.tmpl 1.7 KB
- templates/project/SAGA.tmpl 1.6 KB
- templates/project/STATUS.tmpl 886 B
- templates/project/TEST_CASES.tmpl 2.0 KB
- templates/project/TROUBLESHOOTING.tmpl 2.5 KB
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 · 84 lines · 163 tokens per session scan A a1a7b1836112
docs-project is a skill published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed yesterday), licensed MIT. It adds 163 tokens to every session and 1,427 once invoked, about $0.0008 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-31.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
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…
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.
docs-decisions
Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the…
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…