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/nasrulhazim/claude/project-docsnpx skills add nasrulhazim/claude --skill project-docsgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/project-docs)<a href="https://agentmods.dev/skills/nasrulhazim/claude/project-docs"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/project-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.00199 | $0.03656 |
| Opus 5 | $0.00100 | $0.01828 |
| Sonnet 5 | $0.00040 | $0.00731 |
| Haiku 4.5 | $0.00020 | $0.00366 |
Grade A, and why
project-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.
How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Docs — Full SDLC Documentation Toolchain
Covers the complete software development lifecycle: Pre → During → Post.
All outputs use the numbered folder structure compatible with /docs Claude Code slash command.
Command Reference
| Command | Phase | Description |
|---|---|---|
/docs |
Any | Auto-detect project type, scaffold full structure |
/docs scaffold <type> [--phase] |
Any | Scaffold by project type + SDLC phase |
/docs spec |
Pre | Interview → generate Product Specification |
/docs roadmap |
Pre | Generate versioned roadmap (all formats) |
/docs reorganize |
Any | Reorganize existing docs into numbered standard |
/docs validate |
Any | Validate against standards, report issues |
/docs update-toc |
Any | Refresh all README.md table of contents |
/docs health |
Any | SDLC coverage + quality health report |
/docs support |
Post | Scaffold support cluster (FAQ, triage, SLA, etc.) |
/docs runbook |
Post | Generate ops/deployment runbook with checklists |
/docs release-note [--tldr] |
Post | Release notes from git log |
/docs srs |
Pre | Link to project-requirements skill for full SRS generation |
/docs stories |
Pre | Link to project-requirements skill for user stories |
/docs ci-cd |
Post | Generate CI/CD pipeline documentation |
SDLC Folder Structure
docs/
├── README.md ← Master index
├── 00-product/ ← Pre: spec, PRD, roadmap
│ ├── README.md
│ ├── 01-product-spec.md
│ ├── 02-requirements.md
│ ├── 03-roadmap.md
│ ├── 04-srs.md
│ └── 05-user-stories.md
├── 01-architecture/ ← Pre/During: design, ADRs
│ ├── README.md
│ ├── 01-overview.md
│ ├── 02-patterns.md
│ ├── 03-data-layer.md
│ └── adr/
│ └── 0001-record-architecture-decisions.md
├── 02-development/ ← During: setup, workflows, testing
│ ├── README.md
│ ├── 01-getting-started.md
│ ├── 02-workflows.md
│ ├── 03-testing.md
│ └── 04-livewire-components.md
├── 03-deployment/ ← Post: deploy, ops runbook
│ ├── README.md
│ ├── 01-overview.md
│ ├── 02-runbook.md
│ └── 03-ci-cd.md
├── 04-api/ ← During/Post: contracts
│ ├── README.md
│ └── 01-endpoints.md
└── 05-support/ ← Post: FAQ, triage, SLA, post-mortem
├── README.md
├── 01-faq.md
├── 02-support-workflow.md
├── 03-sla.md
├── 04-post-mortem-template.md
└── 05-deprecation.md
What ships with it
3 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 · 390 lines · 199 tokens per session scan A fdda6aa3e200
project-docs is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 3d ago), licensed MIT. It adds 199 tokens to every session and 3,656 once invoked, about $0.0010 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…