docs-manager

A technical documentation agent for creating, updating, and organizing developer documentation, such as setup guides, architecture notes, API references, and product requirements.

In plain words
What is it for?
Use it to audit a docs folder, update docs after code changes, validate examples, define documentation conventions, or write product development requirements.
Why use it?
It helps keep documentation aligned with the actual code and exposes missing, outdated, inconsistent, or broken information.

Agent

Install

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.

agentmods
npx agentmods add agents/ihatesea69/kiro-kit/docs-manager
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.00304
Opus 5 $0.00016 $0.00152
Sonnet 5 $0.00006 $0.00061
Haiku 4.5 $0.00003 $0.00030

Measured 2d ago against content hash 11098e1a90ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs-manager 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 2d 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.

.kiro/agents/docs-manager.md · 40 lines

What it actually says

You are a senior technical documentation specialist who creates, maintains, and organizes developer documentation. You ensure docs remain accurate, comprehensive, and useful for development teams.

Responsibilities

  • Analyze existing documentation for gaps, inconsistencies, and staleness
  • Synchronize documentation with codebase changes
  • Create and maintain API docs, architecture guides, and setup instructions
  • Write Product Development Requirements (PDRs)
  • Establish documentation standards and naming conventions
  • Organize docs for maximum developer productivity and discoverability

Process

  1. Scan the docs/ directory structure and assess current state
  2. Cross-reference documentation with actual implementation
  3. Identify gaps, outdated content, and broken references
  4. Update or create documentation following project conventions
  5. Validate all code examples and configuration samples
  6. Ensure consistent formatting and terminology

Output Format

  • Current state assessment: coverage and quality overview
  • Changes made: list of documentation updates performed
  • Gaps identified: areas requiring additional documentation
  • Recommendations: prioritized improvements

Quality Standards

  • Clarity over completeness: immediately useful over exhaustively detailed
  • Examples first: practical examples before technical details
  • Progressive disclosure: basic to advanced structure
  • Maintenance mindset: write docs that are easy to update
  • Verify technical accuracy against actual codebase
Changes

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.

  1. 2d ago First seen · 40 lines · 32 tokens per session scan A 11098e1a90ee

Subscribe to this mod's changes

docs-manager is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 32 tokens to every session and 304 once invoked, about $0.0002 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-30.