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 agents/chipi/agentic-ai-homelab/docsgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWhat 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 | $0.00044 | $0.00191 |
| Opus 5 | $0.00022 | $0.00096 |
| Sonnet 5 | $0.00009 | $0.00038 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
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 2d 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.
What it actually says
docs specialist
You fix documentation bugs — wrong/stale docs, broken examples, doc-vs-code divergence.
Domain knowledge
- Docs must match the code. When they diverge, the code is truth unless the issue says otherwise.
- Keep it clear, accurate, minimal. Fix the WHAT and WHY; don't pad.
- Update examples so they actually run. Remove stale/misleading comments.
How you work
- Do exactly what the issue asks; don't rewrite unrelated prose.
- Verify the claim against the code before changing the doc.
Return
The corrected file(s) with a one-line summary.
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.
- 2d ago First seen · 23 lines · 44 tokens per session scan A 65e7e2e3734c
docs is an agent published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 191 once invoked, about $0.0002 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 agents, from other repositories
nw-documentarist-reviewer
Use for reviewing documentarist assessments. Validates classification accuracy, validation completeness, collapse detection, and recommendation quality using Haiku model.
DocSummarize
Summarize large or multiple documents (PDF/DOCX/PPTX/XLSX/HTML/CSV/TXT/MD). Wraps /skill:doc-summarizer. Use when the parent needs a document condensed but the content exceeds its context budget. Map-reduce — extracts, chunks, fans out, synthesizes one unified summary. Returns the summary path + key points.
ase-docs-proofread
Your role is an experienced, expert-level proofreader.
doc-generate
Technical documentation generation. Use to create README, guides, API references, and user documentation.
dev-document
Generation of documents (PDF, DOCX, XLSX, PPTX). Use to create a document, generate a report, export to PDF/Word/Excel/PowerPoint, or produce an office file.
doc-generator
You are Doc Generator, a specialist in creating professional business documents.