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/datatorag/mcp-gateway/claude-mdgit clone --depth 1 https://github.com/datatorag/mcp-gatewayWrote 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/datatorag/mcp-gateway/claude-md)<a href="https://agentmods.dev/instructions/datatorag/mcp-gateway/claude-md"><img src="https://agentmods.dev/badge/instructions/datatorag/mcp-gateway/claude-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.00721 | $0.00721 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
mcp-gateway CLAUDE.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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
datatorag-mcp
This repository is public. Everything committed here — code, docs, skills, agent definitions, commit messages — is visible to the world.
Security gate (mandatory)
Before every git push and before every production deploy:
- Run the
security-revieweragent (.claude/agents/security-reviewer.md) on the outgoing diff (origin/main...HEAD, or the staged/working-tree changes if pushing amends). - Only push/deploy on
VERDICT: PASS. - On
VERDICT: BLOCK, fix the findings first. If a secret is in any commit of the unpushed range, rewrite the range's history (amend or rebase) — deleting it in a follow-up commit is not enough. If a secret was already pushed, treat it as compromised: rotate it, then purge history.
Repo rules
- Never commit secrets, rendered
.envcontent, or credentials of any kind. Production secrets live in AWS SSM Parameter Store and are rendered at deploy time (see.env.exampleheader and the deploy skill). - Never commit internal company documents, compliance evidence, or customer/lead personal data. Internal material belongs in the private company repo, not here.
- Package manager is pnpm. Tests:
pnpm vitest runinapps/gateway; typecheck:pnpm exec tsc --noEmit; production build:pnpm build. - Before pushing, verify the active GitHub account is the org account
(
gh auth status), not a personal one.
Skills & agents
Codebase knowledge lives in .claude/skills/ — load these instead of
re-reading the source:
codebase-map— architecture, flows, decisions, where-things-live. Load first.gateway-dev— recipes for gateway changes + test patterns + ship ritual.site-content— blog/changelog/docs systems and page conventions.services-integrations— Brevo/Slack/Stripe/PostHog/event-pipeline patterns.ops-debugging— prod runbook (placeholder form; live values in memory).gws-mcp-dev— developing the gws-mcp plugin repo + its ship tail.product-capture— Remotion project attools/capturefor product screenshots/recordings; imports real gateway components so captures can't drift.parent-updates— keeping thedatatorag-hqparent session current. It cannot see this session, so an update not sent did not happen.outbound-copy— anything a person outside the company reads: transactional/lifecycle email, in-product strings, form and error copy. Load it (andmanuel-voice) before drafting a line.- Plus:
blog-writing,db-query,deploy,humanizer,marketing-video(brand explainers only),product-promo-video(superseded).
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.
- 5d ago First seen · 56 lines · 721 tokens per session scan A 1f0453465647
mcp-gateway CLAUDE.md is an instructions file published in the GitHub repository datatorag/mcp-gateway (3 stars, last pushed today), licensed MIT. It adds 721 tokens to every session, about $0.0036 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
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.
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).
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.
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).