Borrowing it
Nothing to install: this file belongs to adpena/teadata-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/adpena/teadata-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/adpena/teadata-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/adpena/teadata-mcp/agents-md)<a href="https://agentmods.dev/instructions/adpena/teadata-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/adpena/teadata-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/adpena/teadata-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/adpena/teadata-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.00598 | $0.00598 |
| Opus 5.5 | $0.00239 | $0.00239 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
teadata-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 1mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/teadata_mcp/: Python MCP server code (routing, business logic, SSE entry point).frontend/: Vite + React + TypeScript UI; builds intostatic_dist/for the backend to serve.tests/: Pytest suite (test_*.py).run_dev.sh,run_mcp.sh: local/dev helper scripts;Dockerfilefor deployment.
Build, Test, and Development Commands
./run_dev.sh: build frontend, sync Python deps viauv, runuvicorn(default port8000, auto-selects next free port; override with--port).- Backend only:
uv sync, thenuv run uvicorn teadata_mcp.sse_server:app --reload --port 8000. - Frontend dev server:
cd frontend && npm install --legacy-peer-deps && npm run dev. - Frontend build:
cd frontend && npm run build(writes tostatic_dist/). - Frontend lint:
cd frontend && npm run lint. - Cloudflare tunnel helper:
./run_mcp.sh(use-sto skip frontend build; default port8000, auto-selects next free port; override with--port; requirescloudflared). - Performance/log bundle:
./share_perf_report.sh(writeslogs/share_perf_report_*.txtand copies to clipboard).
Coding Style & Naming Conventions
- Python: 4-space indent, type hints where practical,
snake_casefor modules/functions; keep server code undersrc/teadata_mcp/. - Frontend: 2-space indent in TS/TSX; components in
PascalCase(e.g.,CampusView.tsx), utilities/types incamelCaseortypes.ts. - Styling: Tailwind utility classes in
className; keep new styles colocated with components.
Testing Guidelines
- Framework: pytest in
tests/; run withuv run pytest. - Naming:
test_*.pyandtest_*functions. - Coverage: no explicit threshold; add tests for new tool routes or data engine behavior.
Commit & Pull Request Guidelines
- Commit messages follow short, imperative summaries (e.g., "Add ...", "Document ...", "Fix ..."); keep scope in the body if needed.
- PRs should include: a clear description, linked issue if applicable, test command(s) run, and screenshots/GIFs for UI changes.
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.
- 1mo ago First seen · 35 lines · 598 tokens per session scan A 356869c136de
teadata-mcp AGENTS.md is an instructions file published in the GitHub repository adpena/teadata-mcp (1 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 598 tokens to every session, about $0.0024 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-31.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.