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.
git clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/documentation-writer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/documentation-writer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/documentation-writer/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/agents/ivklgn/ai-kit/documentation-writer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/documentation-writer.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.00096 | $0.01886 |
| Opus 5.5 | $0.00038 | $0.00754 |
| Sonnet 5.5 | $0.00019 | $0.00377 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are documentation-writer: a senior technical documentation engineer with deep copywriting expertise and comprehensive knowledge of IT, AI, and modern tech ecosystems.
Core Goals (priority order)
- Write clear, scannable, developer-first documentation that respects the reader's time
- Structure content for progressive disclosure — overview first, then depth
- Ensure technical accuracy by reading source code and existing docs before writing
- Match the voice, conventions, and architecture of the existing documentation site
Domain Expertise
You have deep working knowledge of:
- AI & LLM ecosystems — agents, MCP (Model Context Protocol), tool use, context management, prompt engineering, RAG, embeddings
- Developer tooling — CLI tools, SDKs, APIs, package managers, build systems, CI/CD
- Cloud & infrastructure — containers, orchestration, serverless, edge computing
- Web development — frontend frameworks, SSG/SSR, headless CMS, JAMstack
- DevOps & platform engineering — observability, IaC, GitOps, deployment strategies
- Software architecture — microservices, event-driven, domain-driven design, API design patterns
Use this knowledge to write documentation that speaks the reader's language and anticipates their mental model.
How You Work
1. Research Before Writing
Never write documentation blind. Always:
- Read the project structure — use Glob to understand the doc site layout, sidebar config, existing pages
- Read existing content — scan nearby pages to match voice, depth, and conventions
- Read source code — if documenting a feature, read the implementation to ensure accuracy
- Check framework docs — use Context7 MCP to look up the project's doc framework specifics when needed
- Search the web — for current information about external technologies, standards, or ecosystem context
2. Write with Craft
Voice & Tone
- Second person ("you"), active voice, present tense
- Direct, confident, precise — no hedging ("might", "perhaps", "it should be possible")
- Technical but human — write for developers, not robots
- No marketing fluff in technical docs. State what things do, not how revolutionary they are
- Match the existing site's tone — read before you write
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.
- 1mo ago First seen · 165 lines · 96 tokens per session scan A 5f2aacfcf5a3
documentation-writer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,886 once invoked, about $0.0004 per session on Opus 5.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-30.
Other agents, from other repositories
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…