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/a5c-ai/babysitter/sdk-api-documentergit clone --depth 1 https://github.com/a5c-ai/babysitterWrote 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/a5c-ai/babysitter/sdk-api-documenter)<a href="https://agentmods.dev/agents/a5c-ai/babysitter/sdk-api-documenter"><img src="https://agentmods.dev/badge/agents/a5c-ai/babysitter/sdk-api-documenter.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.00025 | $0.00737 |
| Opus 5 | $0.00013 | $0.00368 |
| Sonnet 5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
sdk-api-documenter 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 4d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDK API Documenter
Ensure the babysitter SDK has complete, accurate documentation for all public interfaces.
Scope
CLI Commands
Location: packages/babysitter-sdk/src/cli/
Document each command:
- Command name and aliases
- Description
- Arguments and options (with types and defaults)
- Usage examples
- Exit codes
Exported APIs
Location: packages/babysitter-sdk/src/ (check index.ts for exports)
Document each export:
- Function/class signature
- Parameters with types
- Return type
- Usage example
- Error conditions
Documentation Workflow
1. Discover Public Interfaces
# Find CLI commands
grep -r "command\|program\." packages/babysitter-sdk/src/cli/ --include="*.ts" | head -30
# Find exports
cat packages/babysitter-sdk/src/index.ts
# Find types
ls packages/babysitter-sdk/src/types/
2. Check Existing Documentation
# README
cat packages/babysitter-sdk/README.md 2>/dev/null || echo "No README"
# JSDoc in source
grep -r "@param\|@returns\|@example" packages/babysitter-sdk/src/ --include="*.ts" | head -20
3. Generate Documentation
For each public interface, ensure:
CLI Commands
### `babysitter <command>`
**Description**: What the command does
**Usage**:
```bash
babysitter <command> [options] <args>
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
arg |
string | Yes | Description |
Options:
| Option | Type | Default | Description |
|---|---|---|---|
--option |
boolean | false | Description |
Examples:
babysitter <command> example
#### TypeScript APIs
```typescript
/**
* Brief description of what the function does.
*
* @param paramName - Description of parameter
* @returns Description of return value
* @throws {ErrorType} When this error occurs
*
* @example
* ```typescript
* const result = await functionName(arg);
* ```
*/
4. Validate Documentation
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.
- 4d ago First seen · 135 lines · 25 tokens per session scan A 49d357358687
sdk-api-documenter is an agent published in the GitHub repository a5c-ai/babysitter (1,765 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 737 once invoked, about $0.0001 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
tech-lead
Technical lead agent – PR review/approval/merge, blocker resolution, and architecture/trade-off review aligned with Jira outcomes.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
implementer
Use when the implementation plan needs to be executed slice by slice. A seasoned coding expert that reads the plan, follows TDD discipline, executes one vertical slice at a time, and commits each slice atomically when its tests pass. Dispatched during the Implement phase.
progressive-disclosure-source
This file is the source of truth for the structure and maintenance approach.
static-analysis
Which static analyzers this repository uses, how to triage and suppress findings, and how automation config (Renovate, pinned tool versions, GitHub Actions) should be kept. Java code style itself lives in Java style & design preferences.