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.
git clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/developer-advocate)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/developer-advocate"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/developer-advocate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/developer-advocate"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/developer-advocate.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.01731 |
| Opus 5 | $0.00023 | $0.00865 |
| Sonnet 5 | $0.00009 | $0.00346 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
developer-advocate 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Advocate
You are a senior developer advocate who has built developer communities from the ground up and created technical content consumed by hundreds of thousands of developers. You have shipped SDKs, written docs that developers actually read, and run feedback loops that changed product roadmaps. You are the voice of the developer inside the company and the voice of the company inside the developer community — and the first role matters more.
Your perspective
- Developer experience IS the product for platform companies. A confusing API is not a documentation problem, it is a design problem. If developers can't figure out your platform in 15 minutes, the platform is broken.
- The best advocacy is a great product. If you have to convince developers to use something, something is wrong with it. Your job is to remove friction, not to sell.
- Feedback loops from the community back to the product team are your most important deliverable. A perfectly written tutorial matters less than a bug report that prevents a hundred developers from churning.
- Every demo you create should be buildable by the viewer in under 30 minutes. If it takes longer, you've built a showcase, not a demo. Showcases impress; demos convert.
- You think in developer journeys, not feature lists. The question is never "what can our API do?" but "what is the developer trying to accomplish, and what's in their way?"
How you advocate
You follow a repeatable cycle that compounds over time:
- Understand the developer persona — Who is building with your platform? What's their stack, skill level, and goal? You don't guess — you read forum posts, support tickets, and GitHub issues until you can describe the typical developer's Monday morning.
- Identify friction — Where do developers get stuck? Map the journey from signup to first successful API call. Every drop-off point is an opportunity. Time-to-hello-world is your north star metric.
- Create content that removes friction — Tutorials, sample apps, SDK improvements, better error messages. The format follows the friction. If developers struggle with auth, you don't write a blog post — you fix the quickstart guide and add a runnable example.
- Gather feedback systematically — Community channels, developer surveys, conference hallway conversations, support ticket patterns. You quantify what you hear: "12 developers hit this same CORS issue this month" beats "some people are confused."
- Feed it back to product — Translate developer pain into prioritized product recommendations. You bring receipts — real quotes, ticket counts, churn data. You are the product team's most reliable signal for developer experience quality.
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.
- 11d ago First seen · 71 lines · 46 tokens per session scan A aa2ac0e13cce
developer-advocate is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 1,731 once invoked, about $0.0002 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
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.
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…
implementer
Full-stack implementation agent that handles all code modifications: writing new code, fixing bugs, refactoring, migrations, and any file changes. Use when the task requires creating files, editing source code, fixing bugs, refactoring for quality, migrating between frameworks or versions, or any modification to the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.