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/datajourneyhq/mcp/agents-mdgit clone --depth 1 https://github.com/DataJourneyHQ/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/datajourneyhq/mcp/agents-md)<a href="https://agentmods.dev/instructions/datajourneyhq/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/datajourneyhq/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 | $0.00503 | $0.00503 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
MCP AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
There is no established history yet, so start commits with a short imperative summary (≤50 chars), followed by wrapped body text explaining context and follow-up steps. Reference issue numbers (`Closes #12`) when applica How it starts
The opening of the file, as written. The whole thing — 20 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
The Gleam application lives in src/, with datajourney_mcp.gleam bootstrapping Mist, mcp_server.gleam defining MCP tools, router.gleam wiring HTTP/SSE/WebSocket routes, and types.gleam sharing runtime types. Keep new transport code alongside router.gleam, and place reusable helpers in new modules under src/. Tests belong in test/ using mirrored filenames (e.g., test/router_test.gleam). Generated artifacts land in build/; avoid committing edits there.
Build, Test, and Development Commands
Run gleam deps download after pulling new dependencies. Use gleam run to start the Mist server; override PORT via .env when needed. Format code with gleam format before sending patches. Execute gleam test to run the gleeunit suite, or gleam test --target erlang when debugging BEAM output.
Coding Style & Naming Conventions
Adopt the formatter's output (4-space indentation, trailing newline). Modules and functions use snake_case; exposed constants should share that pattern. Custom types and constructors follow PascalCase. Keep public APIs well-documented with /// comments, and group related functions together. Prefer pattern matching and immutable updates to mutable state.
Testing Guidelines
Write unit tests with gleeunit in files ending _test.gleam. Name test functions test_<behavior> and describe assertions clearly. Cover new transports and resource handlers with both happy-path and error cases. When adding external HTTP interactions, stub them in helper modules so tests stay deterministic. Run gleam test locally before pushing.
Commit & Pull Request Guidelines
There is no established history yet, so start commits with a short imperative summary (≤50 chars), followed by wrapped body text explaining context and follow-up steps. Reference issue numbers (Closes #12) when applicable. Pull requests should outline the change, the surfaced MCP capability, and verification steps (gleam test, manual curl). Include screenshots or logs for client-facing 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.
- 3d ago First seen · 20 lines · 503 tokens per session scan A 044eef233590
MCP AGENTS.md is an instructions file published in the GitHub repository DataJourneyHQ/MCP (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 503 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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).
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.