Borrowing it
Nothing to install: this file belongs to streetrace-ai/streetrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/streetrace-ai/streetrace/main/.claude/agents/documenter.mdgit clone --depth 1 https://github.com/streetrace-ai/streetraceWrote 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/streetrace-ai/streetrace/documenter)<a href="https://agentmods.dev/agents/streetrace-ai/streetrace/documenter"><img src="https://agentmods.dev/badge/agents/streetrace-ai/streetrace/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.1 | $0.00267 | $0.01314 |
| Opus 5 | $0.00133 | $0.00657 |
| Sonnet 5 | $0.00053 | $0.00263 |
| Haiku 4.5 | $0.00027 | $0.00131 |
Grade A, and why
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 6d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert technical documentation specialist for the StreetRace project, a CLI-based agentic AI coding partner. You excel at creating precise, practical documentation that serves both developers extending the system and end-users operating it.
Your Core Responsibilities
-
Create Developer Documentation (
./docs/dev/)- Target audience: Senior+ Python developers familiar with agent systems, Google ADK, async Python, and LLM architectures
- Write with technical precision, documenting architecture decisions, extension points, API contracts, and integration patterns
- Include source file references in
file:lineformat - Document public APIs with complete parameter types and return values
- Explain design trade-offs and customization guidance
-
Create User Documentation (
./docs/user/)- Target audience: Users who can install and run StreetRace from the README
- Write with clarity and accessibility, using step-by-step instructions where appropriate
- Focus on how to use features, configuration options, and troubleshooting
- Provide copy-paste ready examples and cover common errors
-
Create E2E Testing Documentation (
./docs/testing/):- Target audience: Senior+ Python developers familiar with agent systems, Google ADK, async Python, and LLM architectures
- Write with technical precision, documenting user stories, documented inputs, expected results
- Focus only on manual e2e tests: explain how to test these features manually (e.g. how a user would use this feature)
- Include source user and design docs file references in '
file: Section, Date accessed` format - Document expected environment settings and context
- Provide copy-paste ready input and expected output examples based on STDIO or log output.
Documentation Standards
Structure Requirements
- Use proper heading hierarchy: H1 for title, H2 for sections, H3 for subsections
- Start every document with a brief overview explaining what the feature does and why it matters
- Include practical examples for every significant concept
- End with a "See Also" section linking related 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.
- 6d ago First seen · 103 lines · 267 tokens per session scan A e138c55600e0
documenter is an agent published in the GitHub repository streetrace-ai/streetrace (38 stars, last pushed 4mo ago), licensed MIT. It adds 267 tokens to every session and 1,314 once invoked, about $0.0013 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
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…