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 instructions/doitintl/doit-mcp-server/agents-mdgit clone --depth 1 https://github.com/doitintl/doit-mcp-serverWrote 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/instructions/doitintl/doit-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/doitintl/doit-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/doitintl/doit-mcp-server/agents-md.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.01687 | $0.01687 |
| Opus 5 | $0.00843 | $0.00843 |
| Sonnet 5 | $0.00337 | $0.00337 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
doit-mcp-server AGENTS.md 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 today.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Public Repo
This repo is public. Do not commit or write into PR titles/descriptions: internal Jira issue keys
(e.g. CMP-1234), names of private/internal repos, or other internal-only details. Keep references
generic (e.g. "a separate private repo") instead.
Environment Setup
Requires Node.js >=18. Install dependencies before running any commands:
yarn install
Project Overview
DoiT MCP Server is a Model Context Protocol (MCP) server that provides LLMs with access to the DoiT API.
This repo is the stdio MCP server plus a transport-independent core package:
-
stdio server (
src/) - Core MCP server implementation using stdio transport- Published as
@doitintl/doit-mcp-serveron npm - Runs locally via
npxor stdio connection - Entry point:
src/index.ts
- Published as
-
Core export (
src/core.ts) - Transport-independent tools, prompts, and utilities- Published as the
@doitintl/doit-mcp-server/coresubpath - Consumed by a remote Cloudflare Worker that lives in a separate private repo
- Published as the
Project Structure
Main Package (src/)
src/
├── index.ts # Entry point (stdio transport)
├── server.ts # MCP server setup and request handlers
├── tools/ # MCP tool implementations
│ └── __tests__/ # Tool tests
├── types/ # Tools and general type definitions
├── utils/ # Shared utilities
│ ├── util.ts # General utilities (debugLog, toSnakeCase, etc.)
│ ├── prompts.ts # MCP prompt definitions
│ ├── consts.ts # Constants
│ ├── toolsHandler.ts # Tool request handler
│ └── __tests__/ # Utility tests
└── __tests__/ # Server-level tests
The remote HTTP/SSE Worker (OAuth, Durable Objects, Streamable HTTP/SSE transport) lives in a
separate private repo and consumes this package's /core export.
Development Commands
Use yarn for all package management and development tasks:
Local Development
yarn check:dev- Run type checking and linting (run after changes)yarn test- Run all testsyarn lint- Check code for linting issuesyarn type-check- Run TypeScript type checking without emitting filesyarn build- Build the project
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.
- today Changed · -1 lines · -9 tokens per session f1e5e115fe6c
- 4d ago First seen · 159 lines · 1,696 tokens per session scan A 689423e1ec8b
doit-mcp-server AGENTS.md is an instructions file published in the GitHub repository doitintl/doit-mcp-server (13 stars, last pushed today), licensed MIT. It adds 1,687 tokens to every session, about $0.0084 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.