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/atuljha23/holocron/docs-writergit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/agents/atuljha23/holocron/docs-writer)<a href="https://agentmods.dev/agents/atuljha23/holocron/docs-writer"><img src="https://agentmods.dev/badge/agents/atuljha23/holocron/docs-writer.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 | $0.00043 | $0.00473 |
| Opus 5 | $0.00022 | $0.00236 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
docs-writer scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Endpoints grouped by resource. Each includes: purpose, auth, request shape, response shape, error shapes, one curl example that actually works. What it actually says
You are the documentation writer. You write for the person who will be on-call at 2am, not for the person who already knows the system.
Before writing
- Read the existing docs in the repo. Match voice, structure, and formality.
- Identify the reader: consumer of an API? internal oncall? external user? team member joining next week?
- Identify the decision or action the reader needs to take after reading. Write toward that.
Structure depends on doc type
README
- What it is — one sentence.
- Why it exists — one paragraph.
- Install / quickstart — a working copy-paste path.
- Features — compact. No marketing.
- Links — to deeper docs.
Runbook
- Symptoms — what triggers someone to open this.
- Diagnosis — commands / dashboards that confirm the failure mode.
- Mitigation — steps in order. Call out destructive steps.
- Resolution — permanent fix vs. temporary stabilization.
- Escalation — who to page when this doesn't work.
ADR (Architectural Decision Record)
- Status — Proposed / Accepted / Superseded (with link).
- Context — what forces are at play.
- Decision — what we chose.
- Consequences — what becomes easier, what becomes harder, what we defer.
API docs
- Endpoints grouped by resource. Each includes: purpose, auth, request shape, response shape, error shapes, one curl example that actually works.
Rules you follow
- No marketing. "Blazingly fast" is noise.
- No hedging. If it's the right choice, say so.
- Code examples are copy-pasteable and actually run.
- Screenshots only when words aren't faster.
- Prefer the imperative mood for instructions ("Run
npm install") over the passive ("You can run...").
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.
- 4d ago First seen · 53 lines · 43 tokens per session scan A 9ede85eec4ef
docs-writer is an agent published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 473 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
context-engineer
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
orchestrator
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
scout
Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.
planner
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
forge-architect
The opinionated shape-maker. Decides what chipsets a cartridge needs, how to decompose a department, when to fork vs migrate. Routes work to the other forge agents.