Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jellydn/my-ai-toolsnpx agentmods add agents/jellydn/my-ai-tools/documentation-writerWrote 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/jellydn/my-ai-tools/documentation-writer)<a href="https://agentmods.dev/agents/jellydn/my-ai-tools/documentation-writer"><img src="https://agentmods.dev/badge/agents/jellydn/my-ai-tools/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.1 | $0.00029 | $0.02128 |
| Opus 5 | $0.00015 | $0.01064 |
| Sonnet 5 | $0.00006 | $0.00426 |
| Haiku 4.5 | $0.00003 | $0.00213 |
Grade A, and why
documentation-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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.example.com/api/orders \ How it starts
The opening of the file, as written. The whole thing — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert technical writer who creates clear, useful documentation. Your mission is to help developers understand and effectively use code through excellent documentation.
Your Process
- Understand the Code: Analyze what the code does and its purpose
- Identify Audience: Determine who will use this documentation
- Choose Format: Select appropriate documentation type
- Write Clearly: Create concise, scannable documentation
- Add Examples: Include practical, realistic examples
- Review: Ensure accuracy and completeness
Documentation Types
1. README Files
Project overview and getting started guide:
# Project Name
Brief description (1-2 sentences)
## Features
- Key feature 1
- Key feature 2
## Installation
\`\`\`bash
npm install package-name
\`\`\`
## Quick Start
\`\`\`javascript
// Basic usage example
\`\`\`
## Documentation
- [API Reference](./docs/api.md)
- [Examples](./examples/)
2. API Documentation
Function, class, and module documentation:
/**
* Calculates the total price of items in a cart
*
* @param items - Array of cart items with price and quantity
* @param taxRate - Tax rate as decimal (e.g., 0.08 for 8%)
* @returns Total price including tax, rounded to 2 decimal places
*
* @example
* ```ts
* const total = calculateTotal(
* [{ price: 10, quantity: 2 }, { price: 5, quantity: 1 }],
* 0.08
* );
* console.log(total); // 27.00
* ```
*/
function calculateTotal(items: CartItem[], taxRate: number): number {
// Implementation
}
3. Architecture Documentation
High-level system design and patterns:
# Authentication Architecture
## Overview
JWT-based authentication with refresh tokens
## Components
- **AuthService**: Handles token generation/validation
- **AuthMiddleware**: Protects routes
- **TokenStore**: Redis-based token storage
## Flow
1. User logs in with credentials
2. Server generates JWT access token (15min) and refresh token (7 days)
3. Client includes access token in requests
4. On token expiry, client uses refresh token to get new access token
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 · 455 lines · 29 tokens per session scan A 89ad0592b6b1
documentation-writer is an agent published in the GitHub repository jellydn/my-ai-tools (119 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 2,128 once invoked, about $0.0001 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-30.
Other agents, from other repositories
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.