MCP: Instructions file for Codex

AGENTS.md

MCP AGENTS.md is an instructions file for Codex, OpenCode from DataJourneyHQ/MCP. It costs 503 tokens per session, scanned A, original, Apache-2.0.

A repository guide for a Gleam application that provides MCP tools over web connections. It documents the project layout, commands, naming rules, and tests.

In plain words
What is it for?
Use it when adding server modules, changing routes, downloading dependencies, formatting code, building the app, or running its test suite.
Why use it?
It gives coding agents clear instructions for changing the right files and running the correct checks in an unfamiliar Gleam project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is DataJourneyHQ/MCP's own configuration. It tells Codex and OpenCode how to work on MCP itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MCP configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DataJourneyHQ/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.

Copy the file
curl -O https://raw.githubusercontent.com/DataJourneyHQ/MCP/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/DataJourneyHQ/MCP

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for MCP AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/datajourneyhq/mcp/agents-md/github.svg)](https://agentmods.dev/instructions/datajourneyhq/mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/datajourneyhq/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/datajourneyhq/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.

agentmods 80×15 button for MCP AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/datajourneyhq/mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/datajourneyhq/mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 503 This file is loaded in full into every session.
When invoked 503 The same file — it is already loaded in full.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00503 $0.00503
Opus 5.5 $0.00201 $0.00201
Sonnet 5.5 $0.00101 $0.00101
Haiku 4.5 $0.00050 $0.00050

Measured 2mo ago against content hash 044eef233590, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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
AGENTS.md · 20 lines

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.

Read the full file on GitHub · 20 lines

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.

  1. 2mo ago First seen · 20 lines · 503 tokens per session scan A 044eef233590

Subscribe to this mod's changes

MCP AGENTS.md is an instructions file published in the GitHub repository DataJourneyHQ/MCP (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 503 tokens to every session, about $0.0020 per session on Opus 5.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.

Related

MCP AGENTS.md compared with instructions from other repositories

MCP AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
MCP AGENTS.mdDataJourneyHQ/MCPInstructions file52d agoApache-2.0A503Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode