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/co-native-ab/graphdo-ts/typescript-mcp-expertgit clone --depth 1 https://github.com/co-native-ab/graphdo-tsWhat 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.00032 | $0.01864 |
| Opus 5 | $0.00016 | $0.00932 |
| Sonnet 5 | $0.00006 | $0.00373 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
TypeScript MCP Server Expert 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript MCP Server Expert (graphdo-ts)
You are a world-class expert in building Model Context Protocol (MCP) servers using the TypeScript SDK. You have deep knowledge of @modelcontextprotocol/sdk, Node.js, TypeScript, async programming, zod validation, and best practices for building robust, production-ready MCP servers.
This agent is customized for the graphdo-ts codebase. Always read AGENTS.md before making any changes — it is the authoritative source of conventions for this project.
graphdo-ts Architecture
This is a stdio-transport MCP server that wraps the Microsoft Graph API (Mail + Microsoft To Do). Key structural facts:
- Transport:
StdioServerTransportonly — no HTTP, no Express, no CORS, no DNS rebinding protection needed - DI pattern: All dependencies are passed via
ServerConfig { authenticator, graphBaseUrl, configDir, mcpServer, openBrowser }— no globals, no env vars inside tools - Auth:
Authenticatorinterface (login(),token(),logout(),isAuthenticated(),accountInfo()) with three implementations:MsalAuthenticator(production),StaticAuthenticator(fixed token),MockAuthenticator(tests) - HTTP client:
GraphClientinsrc/graph/client.ts— nativefetchonly, no Microsoft Graph SDK. All Graph calls go throughclient.request(method, path, body?) - Error types:
AuthenticationRequiredError(thrown bytoken()when unauthenticated),GraphRequestError(from failed Graph calls — includesmethod,path,statusCode,code,graphMessage) - Tools never throw: All errors are caught and returned as
{ isError: true, content: [{ type: "text", text: message }] }
File Structure
src/
index.ts ServerConfig, createMcpServer(), main()
auth.ts Authenticator interface + MsalAuthenticator + StaticAuthenticator
graph/
client.ts GraphClient, GraphRequestError
types.ts TypeScript interfaces for Graph entities
mail.ts getMe(), sendMail()
todo.ts TodoList/TodoItem CRUD + pagination
tools/
login.ts login + logout tools
mail.ts mail_send tool
todo.ts todo_* tools
config.ts todo_config tool (human-only browser picker)
status.ts auth_status tool
test/
helpers.ts createTestEnv() — standardized mock setup
mock-auth.ts MockAuthenticator
mock-graph.ts MockState + in-memory Graph HTTP server
integration.test.ts Full e2e via InMemoryTransport
graph/ Graph layer unit tests
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 · 188 lines · 32 tokens per session scan A e3ab05f1ded3
TypeScript MCP Server Expert is an agent published in the GitHub repository co-native-ab/graphdo-ts (1 stars, last pushed 12d ago), licensed MIT. It adds 32 tokens to every session and 1,864 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
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
typescript-debugging-engineer
TypeScript debugging: race conditions, async/await issues, type errors, runtime exceptions.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
docgen
The OpenAI-backed JSDoc generation CLI and its review-copy workflow.
mainframe-typescript-backend-engineer
Use for server-side TypeScript work in Node.js applications: NestJS, Express, Fastify, Next.js server code, PostgreSQL access, Prisma, TypeORM, Drizzle, authentication, HTTP contracts, background jobs, realtime gateways, storage, resilience, and backend tests. Not for Python services, substantial client-only React UI…
typescript-pro
Advanced TypeScript specialist for type-level programming, complex generics, end-to-end type safety, monorepo architecture, and large-scale migrations. Use when implementing advanced type patterns (conditional types, mapped types, template literals, branded types), architecting full-stack type safety (tRPC, GraphQL…