Borrowing it
Nothing to install: this file belongs to TakoData/tako-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/TakoData/tako-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/TakoData/tako-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/takodata/tako-mcp/agents-md)<a href="https://agentmods.dev/instructions/takodata/tako-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/takodata/tako-mcp/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.1 | $0.02917 | $0.02917 |
| Opus 5 | $0.01458 | $0.01458 |
| Sonnet 5 | $0.00583 | $0.00583 |
| Haiku 4.5 | $0.00292 | $0.00292 |
Grade A, and why
tako-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 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
Tako MCP Server — an MCP (Model Context Protocol) server that provides AI agents access to Tako's knowledge base of 100K+ data visualizations.
The implementation is a single Cloudflare Workers TypeScript server (workers/) deployed at mcp.tako.com (prod) and mcp.staging.tako.com (staging). This is the canonical Tako MCP — all tool work lands here.
Build & Run
Hosted Worker (TypeScript)
cd workers
# Install
npm ci
# Local dev (in-memory, no Cloudflare deploy)
npm run dev
# Deploy (requires CF auth)
npm run deploy:staging
npm run deploy:production
# Verification
npm run typecheck
npm test
npm run registry:check # validate registry/server.json + _registry.ts have no drift
SMOKE_BASE_URL=https://mcp.staging.tako.com TAKO_SMOKE_API_TOKEN=... npm run smoke
Architecture
Hosted (Cloudflare Workers) — workers/
- Framework:
@modelcontextprotocol/sdkwithStreamableHTTPServerTransport - Runtime: Cloudflare Workers (TypeScript,
nodejs_compatflag) - Endpoints: two path-selected MCP surfaces —
POST /mcp(generic, anonymous tier allowed) andPOST /mcp/chatgpt(OAuth-only, the surface submitted to OpenAI) — plusGET /health. The request path picks the surface; nothing reads the client User-Agent (workers/src/surface.ts). - Auth:
Authorization: Bearer <TAKO_API_TOKEN>extracted at request boundary, forwarded to Django asX-API-Key; OAuth 2.1 flow for Claude.ai / ChatGPT - Tool registry: auto-generated from
workers/src/tools/*.tsviaworkers/scripts/gen-registry.ts; outputsworkers/src/tools/_registry.ts,registry/server.json,registry/lhm.plugin.jsonanddocs/TOOLS.mdin lockstep (CI checks all four for drift) - CI:
.github/workflows/workers-ci.yml(typecheck + tests on PRs),workers-deploy.yml(staging on push tomain; production on published GitHub Release, gated by theproductionenvironment; manualworkflow_dispatchfor either env),workers-smoke.yml(auto-smoke after successful staging deploys)
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 Changed · +155 tokens per session 81e7f4eb23a2
- 7d ago First seen · 137 lines · 2,762 tokens per session scan A a9f77e94022c
tako-mcp AGENTS.md is an instructions file published in the GitHub repository TakoData/tako-mcp (5 stars, last pushed 4d ago), licensed MIT. It adds 2,917 tokens to every session, about $0.0146 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 instructions, from other repositories
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.
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.
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).
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.