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/ihatesea69/kiro-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/ihatesea69/kiro-kit/docs-manager)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/docs-manager"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/docs-manager/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/ihatesea69/kiro-kit/docs-manager"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/docs-manager.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.00032 | $0.00304 |
| Opus 5.5 | $0.00013 | $0.00122 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 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.
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
- Scan the
docs/directory structure and assess current state - Cross-reference documentation with actual implementation
- Identify gaps, outdated content, and broken references
- Update or create documentation following project conventions
- Validate all code examples and configuration samples
- 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
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 · 40 lines · 32 tokens per session scan A 11098e1a90ee
docs-manager is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 304 once invoked, about $0.0001 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
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
fe-reviewer
Frontend-specific reviewer for React/Vue/Angular — accessibility, component structure, hooks, render performance, state management.
build-agent
File implementation and modification specialist.