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/emerzon/mtdata-mcp/agents-mdgit clone --depth 1 https://github.com/emerzon/mtdata-mcpWhat 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.00709 | $0.00709 |
| Opus 5 | $0.00354 | $0.00354 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
mtdata-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 2d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Python code lives in src/mtdata/. Runtime setup is in bootstrap/; CLI, MCP, Web API, reporting, regimes, and trading tools are in core/; market access belongs in services/; forecasting and pattern logic live in their named packages; shared schemas and utilities are in shared/ and utils/. The React/Vite client is under webui/src/. Keep tests in tests/, grouped by the corresponding domain (tests/core/, tests/services/, and so on). Documentation belongs in docs/, maintenance utilities in scripts/, and reusable agent prompts in prompts/.
Build, Test, and Development Commands
pip install -e ".[web,pattern-search-hnsw]" pytest ruffinstalls the backend and CI test tools for Python 3.14.ruff check src testsruns Python lint and import-order checks.python scripts/schema_evaluate.pyvalidates public tool schemas.python -m pytest testsruns the backend suite; pass a test path or-k expressionfor focused work.mtdata-webapiserves the API and built UI locally.- From
webui/, runnpm ci,npm run dev,npm test,npm run typecheck, andnpm run buildto install, develop, verify, and package the frontend.
Coding Style & Naming Conventions
Use four spaces in Python, type hints on public interfaces, snake_case for modules/functions, and PascalCase for classes. Ruff rules in pyproject.toml are authoritative. Frontend code uses strict TypeScript, two-space indentation, PascalCase React components, and camelCase hooks/helpers. Preserve established single-quote, semicolon-free TS style.
Testing Guidelines
Pytest files and functions use the test_*.py / test_* pattern. Frontend tests use *.test.ts with Vitest. Add focused regression tests beside the affected domain and cover error paths and public contracts. No numeric coverage threshold is configured; all lint, schema, backend, frontend test, type-check, and build jobs must pass.
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.
- 2d ago First seen · 39 lines · 709 tokens per session scan A 34c25fd0d3dc
mtdata-mcp AGENTS.md is an instructions file published in the GitHub repository emerzon/mtdata-mcp (22 stars, last pushed 2d ago), licensed MIT. It adds 709 tokens to every session, about $0.0035 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
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.
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).
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.