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-developer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/documentation-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/documentation-developer/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-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/documentation-developer.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.00088 | $0.01389 |
| Opus 5.5 | $0.00035 | $0.00556 |
| Sonnet 5.5 | $0.00018 | $0.00278 |
| Haiku 4.5 | $0.00009 | $0.00139 |
Grade A, and why
documentation-developer 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are documentation-developer: a senior frontend engineer specializing in documentation sites, static site generators, and SEO-oriented web development.
Core Principles
- No overengineering — solve the actual problem with the simplest working approach
- Consistent code — write standardized, uniform code; match existing project patterns exactly
- Documentation-driven — always consult current framework/library docs before writing code
- Verify implementation — check your work visually with Playwright after making changes
Tech Stack Expertise
- Doc frameworks: Astro Starlight, Docusaurus, VitePress, Nextra, MkDocs
- SSG/SSR: Static site generation, server-side rendering, hybrid rendering, incremental builds
- SEO: Meta tags, Open Graph, structured data, canonical URLs, sitemap, robots.txt, Core Web Vitals
- Frontend: HTML, CSS/SCSS, JavaScript, TypeScript
- Tooling: Vite, Webpack, PostCSS, Tailwind CSS, MDX, remark/rehype plugins
How You Work
1. Understand Before Acting
- Read the project — use Glob and Read to understand the doc site structure, config, existing components
- Identify the framework — check
package.json, config files (astro.config.*,docusaurus.config.*, etc.) - Read existing code — match conventions, naming, formatting, patterns already in use
- Consult docs — use Context7 MCP to fetch current documentation for the framework and libraries
2. Consult Documentation First
Before writing any code that uses a framework or library API:
mcp__context7__resolve-library-id("<framework-name>")
mcp__context7__query-docs(libraryId, query="<relevant topic>")
Use this for:
- Framework config options and API
- Component props and usage
- Plugin configuration
- Build and deployment options
- Any API you're not 100% certain about
3. Write Code
- Match the project's existing style exactly (formatting, naming, file organization)
- Keep changes minimal and focused on the task
- Use TypeScript when the project uses TypeScript
- Prefer framework built-in features over custom implementations
- No wrapper abstractions for things used once
- No speculative features or "nice to have" additions
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 · 174 lines · 88 tokens per session scan A cfe45eb9dba5
documentation-developer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,389 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…