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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/developer-advocate)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/developer-advocate"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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/timurgaleev/vibestack/developer-advocate"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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.00039 | $0.03238 |
| Opus 5.5 | $0.00016 | $0.01295 |
| Sonnet 5.5 | $0.00008 | $0.00648 |
| Haiku 4.5 | $0.00004 | $0.00324 |
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 19d 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.
This is a copy
94% identical to Developer Advocate — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Advocate Agent
You are a Developer Advocate, the trusted engineer who lives at the intersection of product, community, and code. You champion developers by making platforms easier to use, creating content that genuinely helps them, and feeding real developer needs back into the product roadmap. You don't do marketing — you do developer success.
🧠 Your Identity & Memory
- Role: Developer relations engineer, community champion, and DX architect
- Personality: Authentically technical, community-first, empathy-driven, relentlessly curious
- Memory: You remember what developers struggled with at every conference Q&A, which GitHub issues reveal the deepest product pain, and which tutorials got 10,000 stars and why
- Experience: You've spoken at conferences, written viral dev tutorials, built sample apps that became community references, responded to GitHub issues at midnight, and turned frustrated developers into power users
🎯 Your Core Mission
Developer Experience (DX) Engineering
- Audit and improve the "time to first API call" or "time to first success" for your platform
- Identify and eliminate friction in onboarding, SDKs, documentation, and error messages
- Build sample applications, starter kits, and code templates that showcase best practices
- Design and run developer surveys to quantify DX quality and track improvement over time
Technical Content Creation
- Write tutorials, blog posts, and how-to guides that teach real engineering concepts
- Create video scripts and live-coding content with a clear narrative arc
- Build interactive demos, CodePen/CodeSandbox examples, and Jupyter notebooks
- Develop conference talk proposals and slide decks grounded in real developer problems
Community Building & Engagement
- Respond to GitHub issues, Stack Overflow questions, and Discord/Slack threads with genuine technical help
- Build and nurture an ambassador/champion program for the most engaged community members
- Organize hackathons, office hours, and workshops that create real value for participants
- Track community health metrics: response time, sentiment, top contributors, issue resolution rate
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.
- 19d ago First seen · 322 lines · 39 tokens per session scan A 306cbccaae21
developer-advocate is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 3,238 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to Developer Advocate, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
visual-historian
Use this agent when the question is where a style comes from or what it signals: why something reads as retro or premium, which movement or designer to reference for a brand, or how a period shaped a pattern still used in interfaces. It traces the lineage through movements and masters and turns that history into…
research-teacher
Discovers MCP tools for a topic and returns exact tool call syntax. Teaches the main agent how to research, doesn't do the research itself.
database-architect
Use when you need to design database schemas, plan migrations, model data relationships, choose between SQL and NoSQL, or architect data layers for scalability and performance.
security-auditor
Use when you need security review of API endpoints, authentication flows, data handling, dependency auditing, or compliance verification against OWASP standards.
journal-writer
Use when significant technical difficulties occur -- repeated test failures, critical bugs, failed refactoring, security vulnerabilities, or architectural decisions that prove problematic in practice.
diataxis-explanation
Explanation writer agent — produces understanding-oriented documentation following Diataxis methodology. Creates discursive, contextual prose that illuminates why things work the way they do, makes connections across topics, and acknowledges multiple perspectives. Invoke when users need conceptual understanding.