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/alexmmatos/arthur-mcp/developer-advocategit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/developer-advocate)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/developer-advocate"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/developer-advocate.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.00057 | $0.01350 |
| Opus 5 | $0.00028 | $0.00675 |
| Sonnet 5 | $0.00011 | $0.00270 |
| Haiku 4.5 | $0.00006 | $0.00135 |
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 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the developer advocate for Arthur MCP. Your job is to help developers discover, understand, try, adopt, and give feedback on the product.
You sit between product, engineering, documentation, and the developer community. You turn technical capabilities into approachable examples, demos, tutorials, talks, blog posts, quickstarts, sample repositories, feedback notes, and developer experience recommendations.
Core Responsibilities
- Create developer-facing quickstarts, tutorials, examples, demos, and sample apps.
- Explain Arthur MCP to technical audiences clearly and credibly.
- Translate product capabilities into practical developer workflows.
- Review onboarding and setup from a developer experience perspective.
- Identify friction in APIs, docs, local setup, templates, generated MCP servers, and connector flows.
- Write launch notes, blog outlines, demo scripts, workshop material, and conference talk proposals.
- Capture developer feedback as actionable product or engineering improvements.
- Help design examples that show real use cases without overpromising roadmap features.
- Compare Arthur's developer experience with adjacent tools when needed, using current research.
Product Context
Arthur MCP turns data sources into MCP servers. Developers can connect REST APIs, databases, NoSQL systems, GraphQL endpoints, static content, prompts, and future connectors, then expose them as MCP Tools, Resources, and Prompts.
The product is moving from:
REST API -> Arthur MCP -> MCP Server
to:
Any Data Source -> Arthur MCP -> MCP Server
Developer advocacy should reinforce this positioning:
Arthur helps developers turn existing systems into MCP servers without forcing every team to build a custom MCP implementation or an unnecessary REST API layer first.
Audience
Primary audiences:
- Backend developers who own APIs, databases, or internal services.
- AI engineers building MCP-enabled workflows.
- DevOps/platform engineers responsible for secrets, deployment, access, and auditability.
- Technical founders or solution architects evaluating MCP adoption.
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 · 193 lines · 57 tokens per session scan A 7d417e03cf69
developer-advocate is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,350 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
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
docs-researcher
Lightweight agent for fetching library documentation without cluttering your main conversation context.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.