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 ngocsangyem/MeowKit --skill docs-initgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/docs-init)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/docs-init"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/docs-init/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/ngocsangyem/meowkit/docs-init"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/docs-init.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.00066 | $0.00906 |
| Opus 5 | $0.00033 | $0.00453 |
| Sonnet 5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
mk:docs-init 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Init
Generate initial project documentation from codebase analysis.
Scope: Creates docs/ from scratch. For updating existing docs → mk:document-release.
Also run
mk:project-contextto generate the agent-constitution file (docs/project-context.md).mk:docs-initgenerates the full documentation suite;mk:project-contextgenerates only the constitution.
When to Use
- Project has no
docs/directory docs/exists but is empty or has only stubs- User asks to "initialize docs", "create documentation", "generate docs"
- After
mk:bootstrapcompletes (new project needs docs)
Do NOT invoke when: docs already exist and need updating (use mk:document-release).
Process
- Check existing state — does
docs/exist? Are files already populated?- If populated docs exist → suggest
mk:document-releaseinstead, stop.
- If populated docs exist → suggest
- Scout codebase — activate
mk:scoutto analyze project structure. Skip:.claude/,.git/,node_modules/,__pycache__/,dist/,build/ - Merge findings — consolidate scout reports into context for doc generation
- Generate docs — spawn
documentersubagent via Task tool with scout context. Output files (adapt to what the project actually has):README.md— project overview (≤300 lines)docs/project-overview.md— what this project is, who it's fordocs/codebase-summary.md— directory map, key modules, entry pointsdocs/code-standards.md— conventions found in codebasedocs/architecture/system-architecture.md— component diagram, data flow Optional (generate only if relevant):docs/deployment-guide.md— if CI/CD or Docker config detecteddocs/design-guidelines.md— if frontend/UI code detected
- Size check — run
wc -l docs/*.md | sort -rn. Flag files >800 lines. - Report — print generated files list with line counts.
Hard gate: Do NOT write code or implementation. Only documentation.
Gotchas
- Hallucinating architecture: generating docs about code that doesn't exist → always scout FIRST, generate from findings only
- Over-documenting small projects: creating 7 docs for a 50-line script → check project size; small projects get README + codebase-summary only
- Stale on first run: docs describe initial state but drift immediately → tell user to run
mk:document-releaseafter each feature ship
What ships with it
1 file 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.
- 8d ago First seen · 96 lines · 66 tokens per session scan A e731b44fae0d
mk:docs-init is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 906 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
daily-report-generator
Automatically generate daily construction reports from field data, worker inputs, weather, and progress photos. Creates professional PDF reports.
payment-application-processor
Process construction payment applications. Validate schedule of values, calculate retainage, track billing status, and generate G702/G703 forms.
dgn-to-excel
Convert DGN files (v7-v8) to Excel databases. Extract elements, levels, and properties from infrastructure CAD files.
dwg-to-excel
Convert AutoCAD DWG files (1983-2026) to Excel databases using DwgExporter CLI. Extract layers, blocks, attributes, and geometry data without Autodesk licenses.
ifc-to-excel
Convert IFC files (2x3, 4x1, 4x3) to Excel databases using IfcExporter CLI. Extract BIM data, properties, and geometry without proprietary software.
payment-application-generator
Generate AIA-style payment applications. Track schedule of values, calculate retention, and produce payment documentation.