Borrowing it
Nothing to install: this file belongs to Teamwork/mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Teamwork/mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Teamwork/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/instructions/teamwork/mcp/agents-md)<a href="https://agentmods.dev/instructions/teamwork/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/teamwork/mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/teamwork/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/teamwork/mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.24231 | $0.24231 |
| Opus 5.5 | $0.09692 | $0.09692 |
| Sonnet 5.5 | $0.04846 | $0.04846 |
| Haiku 4.5 | $0.02423 | $0.02423 |
Grade A, and why
mcp 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 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.
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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
A concise guide for AI coding agents working on this repository. It complements README.md with machine-actionable build, test, run, and convention notes.
This repository is public
Everything committed here is world-readable and permanent — source, comments, tests, docs, commit messages, PR titles and descriptions, issue text. A later fix does not retract what has already been cloned, cached or indexed. This file is public too, and is bound by its own rules.
Using an internal source to get the behaviour right is fine; publishing it is not. Only the externally observable result belongs in the repo.
- Never name private repositories or services.
desksdkgo,twapi-go-sdkand the MCP SDK are public and may be cited freely. The backends behind the Projects and Desk APIs are not — do not name their repositories, packages, files, handlers, models, or query-argument identifiers. Describe the HTTP endpoint instead: route, parameters, JSON keys, status codes. - Never name internal infrastructure. Deployments, hostnames, dashboards, monitoring, CI tooling, chat channels, wikis, runbooks, or environment detail beyond the documented
TW_MCP_ENVvalues. - Never reference internal tracking. Ticket keys, incident IDs, or links and commit hashes in private repositories. Public protocol references (
SEP-2575) are fine — those are published. - Never describe a backend defect as a defect. State what the endpoint does today ("list endpoints clamp
pageSizeover 100 to 100"), not that it is a bug, what causes it, or when it is due to be fixed — the service is still running the old code. - Never publish unreleased information. Roadmap items, planned deprecations, dated fixes, feature flags, or capacity and traffic figures.
- Never commit real data. Tokens, API keys, cookies, real installation subdomains, or real customer and employee names, emails and IDs — in code, tests, fixtures, log samples and error strings alike. Fixtures use
example.com,test.teamwork.com,[email protected], and IDs like777/12345.
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 · +28 tokens per session 661ab3e96cb3
- 12d ago Changed · +2 lines · +131 tokens per session e7615bc14529
- 23d ago Changed · +3 lines · +808 tokens per session 45b72a5cc3db
- 24d ago Changed · +2 lines · +703 tokens per session ba2d57e95d66
- 26d ago Changed · +1 lines · +76 tokens per session d8603e367b70
- 29d ago Changed · +2 lines · +519 tokens per session a130c26c0f50
- 1mo ago Changed · +93 tokens per session 831edc01a41d
- 1mo ago Changed · +4 lines · +760 tokens per session fcf31c119e11
- 1mo ago Changed · +1 lines · +425 tokens per session 37092905dd32
- 1mo ago First seen · 283 lines · 20,688 tokens per session scan A 887365d2e252
mcp AGENTS.md is an instructions file published in the GitHub repository Teamwork/mcp (27 stars, last pushed 2d ago), licensed MIT. It adds 24,231 tokens to every session, about $0.0969 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.