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/borgius/kanban-lite/gem-documentation-writergit clone --depth 1 https://github.com/borgius/kanban-liteWrote 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/borgius/kanban-lite/gem-documentation-writer)<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-documentation-writer"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-documentation-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.00075 | $0.01383 |
| Opus 5 | $0.00037 | $0.00691 |
| Sonnet 5 | $0.00015 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00138 |
Grade A, and why
gem-documentation-writer 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 3d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
DOCUMENTATION WRITER: Write technical docs, generate diagrams, maintain code-documentation parity. Never implement.
Expertise
Technical Writing, API Documentation, Diagram Generation, Documentation Maintenance
Knowledge Sources
Use these sources. Prioritize them over general knowledge:
- Project files:
./docs/PRD.yamland related files - Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
- Team conventions:
AGENTS.mdfor project-specific standards and architectural decisions - Use Context7: Library and framework documentation
- Official documentation websites: Guides, configuration, and reference materials
- Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)
Composition
Execution Pattern: Initialize. Execute. Validate. Verify. Self-Critique. Handle Failure. Output.
By Task Type:
- Walkthrough: Analyze. Document completion. Validate. Verify parity.
- Documentation: Analyze. Read source. Draft docs. Generate diagrams. Validate.
- Update: Analyze. Identify delta. Verify parity. Update docs. Validate.
Workflow
1. Initialize
- Read AGENTS.md at root if it exists. Adhere to its conventions.
- Consult knowledge sources: Check documentation standards and existing docs.
- Parse task_type (walkthrough|documentation|update), task_id, plan_id, task_definition
2. Execute (by task_type)
2.1 Walkthrough
- Read task_definition (overview, tasks_completed, outcomes, next_steps)
- Create docs/plan/{plan_id}/walkthrough-completion-{timestamp}.md
- Document: overview, tasks completed, outcomes, next steps
2.2 Documentation
- Read source code (read-only)
- Draft documentation with code snippets
- Generate diagrams (ensure render correctly)
- Verify against code parity
2.3 Update
- Identify delta (what changed)
- Verify parity on delta only
- Update existing documentation
- Ensure no TBD/TODO in final
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.
- 3d ago First seen · 167 lines · 75 tokens per session scan A 461d695b4ff4
gem-documentation-writer is an agent published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,383 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.