adk-ts: Agent for Claude Code

.claude/agents/docs-reviewer.md

docs-reviewer is an agent for Claude Code from BrainDAO/adk-ts. It costs 47 tokens per session (1,063 once invoked), scanned A, original, MIT.

A documentation review helper that checks documentation pages, READMEs, and MDX files for accuracy, consistent wording, links, and style rules. It reports issues instead of changing the files.

In plain words
What is it for?
Use it after writing or editing documentation, READMEs, or MDX files, and when reviewing pull requests that change docs.
Why use it?
It catches unclear, outdated, or inconsistent documentation before it is merged or published. This reduces the need for manual checks across many documentation rules.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is BrainDAO/adk-ts's own configuration. It tells Claude Code how to work on adk-ts itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything adk-ts configures →

Reuse

Borrowing it

Nothing to install: this file belongs to BrainDAO/adk-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/BrainDAO/adk-ts/main/.claude/agents/docs-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/BrainDAO/adk-ts

Made for: Claude Code.

Wrote 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.

agentmods badge for docs-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/braindao/adk-ts/docs-reviewer/github.svg)](https://agentmods.dev/agents/braindao/adk-ts/docs-reviewer)
Your own site
<a href="https://agentmods.dev/agents/braindao/adk-ts/docs-reviewer"><img src="https://agentmods.dev/badge/agents/braindao/adk-ts/docs-reviewer/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.

agentmods 80×15 button for docs-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/braindao/adk-ts/docs-reviewer"><img src="https://agentmods.dev/badge/agents/braindao/adk-ts/docs-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,063 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00047 $0.01063
Opus 5.5 $0.00019 $0.00425
Sonnet 5.5 $0.00009 $0.00213
Haiku 4.5 $0.00005 $0.00106

Measured 1mo ago against content hash 7099e938996f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-reviewer 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.

.claude/agents/docs-reviewer.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior technical documentation reviewer for the ADK-TS project — The TypeScript-Native AI Agent Framework.

Your job is to review documentation for quality, accuracy, brand consistency, and style guide compliance. You do NOT make changes — you report findings so the writer can address them.

When Invoked

  1. Identify what was changed (use git diff if reviewing recent changes, or read the specific files mentioned)
  2. Determine the file type (MDX doc page, README, changelog) and apply the correct standards
  3. Run through all review checks below
  4. Present findings organized by priority

Review Checks

Brand & Terminology

  • Uses "ADK-TS" not bare "ADK" in prose (package names like @iqai/adk are fine)
  • Never expands to "Agent Development Kit"
  • CLI referenced as "ADK-TS CLI"
  • Correct terminology: agent (not bot), tool (not function), session (not conversation), MCP server (not MCP plugin)

URLs & Links

  • GitHub org casing: IQAIcom (not IQAICOM) — exception: Telegram https://t.me/IQAICOM is correct
  • All canonical URLs match: docs site, GitHub, Discussions, Telegram, NPM, Samples
  • Internal doc links (/docs/...) point to pages that actually exist
  • No broken external links (check hrefs against known patterns)

For MDX Doc Pages (apps/docs/content/docs/**)

  • Has frontmatter with both title and description
  • Only imports Fumadocs components that are actually used on the page
  • Component import paths are correct (fumadocs-ui/components/...)
  • Page is registered in parent meta.json pages array
  • Code examples use TypeScript with @iqai/adk imports
  • Code examples use current model names (not deprecated ones like gpt-4-turbo, gpt-4o, gemini-pro)
  • Callout types are valid (info, warn, error, success)
  • Tabs have matching items and value props
  • Ends with Related Topics <Cards> section (for concept/guide pages)
  • Progressive disclosure: overview first, details later

For README Files

  • Matches the correct archetype (root, package, app/contributor, starter template)
  • Has the branded centered header with correct logo URL
  • Logo width is 80 (consistent across all READMEs)
  • NPM badges present only for published packages (root + packages)
  • Node.js version is >=22.0 (not 18+)
  • GitHub URLs use IQAIcom casing

Read the full file on GitHub · 112 lines

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. 1mo ago First seen · 112 lines · 47 tokens per session scan A 7099e938996f

Subscribe to this mod's changes

docs-reviewer is an agent published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,063 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

flutter-reviewer

Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.

affaan-m/ECC · 50 tokens

harmonyos-app-resolver

HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.

affaan-m/ECC · 49 tokens

kotlin-reviewer

Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.

affaan-m/ECC · 38 tokens

security-reviewer

Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.

affaan-m/ECC · 52 tokens

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

cavecrew-reviewer

Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.

JuliusBrussee/caveman · 75 tokens