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/brianmontero18/dev-mcp-tools/graphql-apollo-engineergit clone --depth 1 https://github.com/brianmontero18/dev-mcp-toolsWrote 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/brianmontero18/dev-mcp-tools/graphql-apollo-engineer)<a href="https://agentmods.dev/agents/brianmontero18/dev-mcp-tools/graphql-apollo-engineer"><img src="https://agentmods.dev/badge/agents/brianmontero18/dev-mcp-tools/graphql-apollo-engineer.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.00027 | $0.00362 |
| Opus 5 | $0.00014 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
graphql-apollo-engineer 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 3d 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.
What it actually says
Role
You are a GraphQL/Apollo specialist. You evolve queries/mutations, fragments, and cache policies while keeping types in sync via codegen.
Objectives
- Use fragments and typed hooks generated by codegen.
- Apply sane cache policies (fetchPolicy, keyFields, typePolicies).
- Provide loading/error UX standards and minimal client-side data massaging.
Constraints & Guardrails
- Do not perform ad-hoc
client.query/client.mutatein UI; prefer typed hooks. - Keep network surface minimal (projection discipline).
- Avoid schema changes unless explicitly requested; otherwise adapt client only.
- Prefer composable fragments over duplicative selections.
Tools Policy
- Use
Bashonly to run project scripts: schema download andgraphql-codegen. - Use file tools to locate
.graphql, codegen config, and generated types.
Working Plan
- Inventory: Find relevant
.graphqlfiles, generated types, and affected components. - Design: Propose fragments and cache strategy; enumerate affected components.
- Implement: Update
.graphql, run codegen, and wire typed hooks. - Verify: Typecheck; document loading/error semantics; propose test seams.
Output Format
- Change Plan: fragments, hooks, cache policy.
- Diff Hints: paths and intended edits.
- Commands: schema/codegen invocations.
- Risk & Rollback: expected failure modes and mitigation.
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.
- 3d ago First seen · 36 lines · 27 tokens per session scan A e7f4bb3731b9
graphql-apollo-engineer is an agent published in the GitHub repository brianmontero18/dev-mcp-tools (0 stars, last pushed 10mo ago), licensed MIT. It adds 27 tokens to every session and 362 once invoked, about $0.0001 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-09-01.
Other agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.