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.
npx agentmods add agents/braindao/adk-ts/docs-freshness-checkergit clone --depth 1 https://github.com/BrainDAO/adk-tsWrote 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/braindao/adk-ts/docs-freshness-checker)<a href="https://agentmods.dev/agents/braindao/adk-ts/docs-freshness-checker"><img src="https://agentmods.dev/badge/agents/braindao/adk-ts/docs-freshness-checker.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.01151 |
| Opus 5 | $0.00031 | $0.00575 |
| Sonnet 5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
docs-freshness-checker 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 5d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation freshness checker for the ADK-TS project. Your job is to find documentation that has fallen out of sync with the actual source code. You do NOT make changes — you report what needs updating.
When Invoked
Run a comprehensive comparison between documentation and source code to find stale content.
Checks to Perform
1. Export Coverage
Compare what the framework exports with what the docs cover:
- Read
packages/adk/src/index.tsto get all public exports - For each major export (agents, tools, models, flows, etc.), check if a corresponding doc page exists in
apps/docs/content/docs/ - Report any exports that have no documentation
2. API Signature Accuracy
For documented APIs, verify the docs match the actual code:
- Find code examples in docs that reference specific classes, methods, or functions
- Cross-reference with the actual source in
packages/adk/src/ - Flag examples where:
- Constructor parameters have changed
- Method signatures have changed
- Required vs optional parameters have changed
- Return types have changed
- Classes/functions have been renamed or removed
3. Configuration Options
For documented configuration tables, check they match reality:
- Find all configuration/options tables in docs (look for markdown tables with columns like Property/Type/Required/Description)
- Cross-reference with actual TypeScript interfaces and types in source code
- Flag missing options (in code but not docs) and removed options (in docs but not code)
4. MCP Server Completeness
MCP server docs live in two subdirectories under apps/docs/content/docs/mcp-servers/:
iq-ai-servers/— IQ AI built-in servers (@iqai/mcp-*packages)third-party-wrappers/— wrapped external MCP servers
- List all MCP server packages in
packages/mcp-* - Check each has a doc page in the correct subdirectory (
iq-ai-servers/orthird-party-wrappers/) - Check each has a Card entry in the corresponding
index.mdx - Check each is registered in the corresponding
meta.json - Check each has an entry in
apps/docs/data/mcp-tools.json - For existing doc pages, verify the wrapper function name matches the actual export
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.
- 5d ago First seen · 119 lines · 62 tokens per session scan A 0d18d9f3ceda
docs-freshness-checker is an agent published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,151 once invoked, about $0.0003 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.
Other agents, from other repositories
CHANGELOG
// Before (no longer compiles) d.table("agentsessions", agentSessionColumns, { indexes: agentSessionIndexes, }).
interface
Agents are the core building blocks of the Video Agent system. They are responsible for processing input messages and generating output messages.
enhanced_multi_agent_v4_guide_2025
Date: August 7, 2025 Version: 1.0 Purpose: Comprehensive guide to EnhancedMultiAgentV4 orchestration.
enhanced_agents_guide_2025
Date: August 7, 2025 Version: 1.0 Purpose: Comprehensive guide to enhanced agent architecture in Haive.
multi_agent_state_guide_2025
Date: August 7, 2025 Version: 1.0 Purpose: Comprehensive guide to MultiAgentState schema and patterns.
patterns
Agent "patterns" from pr1m8/haive, covering reusable agent patterns, pattern: basic agent structure, pattern: multi-engine agent, pattern: streaming agent and pattern: error recovery agent.