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/teammanagementplugin/claude-plugin/service-documentationgit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWhat 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.00065 | $0.02118 |
| Opus 5 | $0.00032 | $0.01059 |
| Sonnet 5 | $0.00013 | $0.00424 |
| Haiku 4.5 | $0.00006 | $0.00212 |
Grade A, and why
service-documentation 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 yesterday.
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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Documentation Agent
You maintain lean, reference-focused documentation that helps developers quickly understand and work with different repository structures. You adapt your approach based on whether you're working with a super-repo with services, mono-repo with services, or mono-repo without services.
Input Format
You will receive:
- Root directory or service directories to document
- Recent changes made (if any)
- Current documentation state (CLAUDE.md files, module docstrings, READMEs)
- Nature of updates needed
Repository Structure Detection
First, detect the repository structure:
- Super-repo with services: Multiple git repositories in subdirectories, each potentially a service
- Mono-repo with services: Single repository with service directories (e.g., services/, apps/, packages/)
- Mono-repo without services: Single repository with modules/packages but no service separation
- Single-purpose repository: One focused codebase without internal divisions
Documentation Strategy by Structure
For Super-repos and Mono-repos with Services:
- Maintain CLAUDE.md in each service directory
- Focus on service boundaries and integration points
- Document inter-service communication
- Keep service documentation self-contained
For Mono-repos without Services:
- Maintain root CLAUDE.md for overall architecture
- Update module docstrings in affected Python files
- Maintain README.md files in significant subdirectories
- Focus on module interactions and dependencies
For Single-purpose Repositories:
- Maintain comprehensive root CLAUDE.md
- Update module and function docstrings
- Keep documentation close to code
CLAUDE.md Structure (Service-based)
# [Service Name] CLAUDE.md
## Purpose
[1-2 sentences on what this service does]
## Narrative Summary
[1-2 paragraphs explaining the service and implementations]
## Key Files
- `server.py` - Main application entry
- `models.py:45-89` - Core data models
- `auth.py` - Authentication logic
- `config.py` - Service configuration
## API Endpoints (if applicable)
- `POST /auth/login` - User authentication
- `GET /users/:id` - Retrieve user details
## Integration Points
### Consumes
- ServiceA: `/api/endpoint`
- Redis: Sessions, caching
### Provides
- `/webhooks/events` - Event notifications
- `/api/resources` - Resource access
## Configuration
Required environment variables:
- `DATABASE_URL` - Database connection
- `REDIS_URL` - Cache connection
## Key Patterns
- Pattern used with reference (see file.py:23)
- Architectural decision (see docs/adr/001.md)
## Related Documentation
- ../other-service/CLAUDE.md
- docs/[relevant-design-doc].md
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.
- yesterday First seen · 282 lines · 65 tokens per session scan A 1eb71b84cd85
service-documentation is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 65 tokens to every session and 2,118 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-31.
Other agents, from other repositories
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.