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 skills/bryanweaver/claude-agent-kit/team-init-docsnpx skills add bryanweaver/claude-agent-kit --skill team-init-docsgit clone --depth 1 https://github.com/bryanweaver/claude-agent-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/skills/bryanweaver/claude-agent-kit/team-init-docs)<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-init-docs"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-init-docs.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.00012 | $0.00368 |
| Opus 5 | $0.00006 | $0.00184 |
| Sonnet 5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
team-init-docs 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 3d 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
Initialize Documentation
Create comprehensive, well-organized documentation for the codebase.
Target area: $ARGUMENTS
Execution
With Agent Teams (recommended)
Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Create a team and spawn teammates:
- Create team named
init-docs - Spawn teammates: documentor
Create the following task list:
| # | Task | Owner | Blocked By |
|---|---|---|---|
| 1 | Analyze codebase structure, frameworks, and architecture | documentor | — |
| 2 | Create docs/ directory structure and generate documentation | documentor | 1 |
| 3 | Build table of contents and cross-link all documents | documentor | 2 |
Without Agent Teams (fallback)
Execute using the Task tool:
Task(documentor, "Initialize comprehensive documentation for the codebase. Focus area: $ARGUMENTS. Analyze project structure, create docs/ folder hierarchy, generate documentation for all major modules, and build a table of contents with cross-links.")
Expected Output
After completion, the docs/ folder should contain:
docs/README.md— main table of contentsdocs/architecture/— system design documentationdocs/api/— API documentation (if applicable)docs/guides/— how-to guidesdocs/reference/— configuration and reference material- Cross-linked documents for easy navigation
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.
- 3d ago First seen · 49 lines · 12 tokens per session scan A f1aae44e51b8
team-init-docs is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 368 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…