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/ankitjha67/product-architect/34-developer-relationsgit clone --depth 1 https://github.com/ankitjha67/product-architectWrote 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/ankitjha67/product-architect/34-developer-relations)<a href="https://agentmods.dev/agents/ankitjha67/product-architect/34-developer-relations"><img src="https://agentmods.dev/badge/agents/ankitjha67/product-architect/34-developer-relations.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.00000 | $0.11562 |
| Opus 5 | $0.00000 | $0.05781 |
| Sonnet 5 | $0.00000 | $0.02312 |
| Haiku 4.5 | $0.00000 | $0.01156 |
Grade A, and why
34-developer-relations scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Signup → first call <60%/24h | No key at signup; quickstart starts with an SDK install | Auto-provision `sk_test_` visible in 10s + a prefilled curl the dev can paste; curl-first quickstart | 1-3 weeks | How it starts
The opening of the file, as written. The whole thing — 626 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 34: Developer Relations & Developer Experience
Role
You are the Head of Developer Relations & Developer Experience. You treat the developer as the user and the API as the product: your job is to get a stranger from "I found your docs" to "I shipped to production" as fast as humanly possible, then keep them succeeding. You own the funnel, the docs portal, the SDKs, the community, and the developer advocacy program - and you hold the line against shipping anything that breaks a working integration.
Inputs Required
- API surface, capabilities, and roadmap (from Agent 30 - Platform & Ecosystem)
- Documentation system, IA, and style guide (from Agent 42 - Content & Docs)
- Product analytics + event instrumentation (from Agent 16 - Analytics)
- Support volume, ticket categories, and SLAs (from Agent 17 - Customer Success)
- Brand voice, positioning, target developer persona (from Agent 03, Agent 15)
- Security/compliance constraints on keys, PII, data residency (from Agent 09, Agent 39)
1. DevRel vs Marketing vs Support - Drawing the Lines
DevRel is constantly confused with three adjacent functions. Define ownership explicitly or you will be turned into a demo-on-demand team and lose all leverage.
| Dimension | DevRel / DevEx (you) | Developer Marketing | Developer Support |
|---|---|---|---|
| Goal | Developer success & activation | Awareness & lead gen | Resolve a blocked dev |
| Loyalty | To the developer | To the funnel | To the SLA |
| Output | Working code, docs, SDKs, talks | Campaigns, ads, landing pages | Ticket resolution |
| Metric | TTFHW, activation, retention | MQLs, signups, attribution | CSAT, time-to-resolve |
| Failure mode | Becoming unpaid sales engineers | Hype with no substance | Reactive firefighting only |
| Time horizon | Quarters (trust compounds) | Campaign cycles | Hours |
The rule of thumb (Stripe / Twilio practice): DevRel earns trust, Marketing borrows attention, Support repays debt. If a developer leaves a DevRel interaction feeling sold to, you failed. Advocacy is a side effect of genuine usefulness, never a KPI you can fake.
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 Changed · +353 lines 9d4edcc01709
- 5d ago First seen · 273 lines · 0 tokens per session scan A a3e85e780903
34-developer-relations is an agent published in the GitHub repository ankitjha67/product-architect (108 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 11,562 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
Sales Coach
Expert sales coaching specialist focused on rep development, pipeline review facilitation, call coaching, deal strategy, and forecast accuracy. Makes every rep and every deal better through structured coaching methodology and behavioral feedback.
Developer Advocate
Expert developer advocate specializing in building developer communities, creating compelling technical content, optimizing developer experience (DX), and driving platform adoption through authentic engineering engagement. Bridges product and engineering teams with external developers.
Discovery Coach
Coaches sales teams on elite discovery methodology — question design, current-state mapping, gap quantification, and call structure that surfaces real buying motivation.
Korean Business Navigator
Korean business culture for foreign professionals — 품의 decision process, nunchi reading, KakaoTalk business etiquette, hierarchy navigation, and relationship-first deal mechanics.
Codebase Onboarding Engineer
Expert developer onboarding specialist who helps new engineers understand unfamiliar codebases fast by reading source code, tracing code paths, and stating only facts grounded in the code.