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/omelet-ai/tms-dev-mcp/agents-mdgit clone --depth 1 https://github.com/omelet-ai/tms-dev-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/omelet-ai/tms-dev-mcp/agents-md)<a href="https://agentmods.dev/instructions/omelet-ai/tms-dev-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/omelet-ai/tms-dev-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.1 | $0.01535 | $0.01535 |
| Opus 5 | $0.00767 | $0.00767 |
| Sonnet 5 | $0.00307 | $0.00307 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
tms-dev-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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
def fetch(url: str | None = None) -> dict[str, Any] | None: ... Copies of this mod
1 near-identical copy found in the catalogue:
- tms-dev-mcp CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Overview
Python MCP (Model Context Protocol) server providing tools to explore Omelet's Routing Engine and iNavi's Maps API for building Transport Management Systems. Built with FastMCP framework.
Provider Environment Notes
- iNavi Maps API: Use the production base URL (
https://imaps.inavi.com) for runtime API calls, but keep the documentation URL pointed at the development docs host (https://dev-imaps.inavi.com/api-docs). Generated docs and tooling expect this split.
Build/Lint/Test Commands
Environment Setup
uv sync --all-groups # Install all dependencies (dev + test groups)
source .venv/bin/activate # Activate venv (Unix)
pre-commit install # Install git hooks
Testing
uv run pytest -c setup.cfg # Run all tests
uv run pytest tests/test_tools/test_doc_tools.py # Run single file
uv run pytest tests/test_tools/test_doc_tools.py::TestGetBasicInfo # Run single class
uv run pytest tests/test_tools/test_doc_tools.py::TestGetBasicInfo::test_masks_api_keys # Single test
uv run pytest -k "test_rejects" # Run tests matching pattern
uv run pytest -v # Verbose output
uv run pytest --tb=short # Short traceback
Linting & Type Checking
uv run ruff check . # Lint (will auto-fix with --fix)
uv run ruff format . # Format code
uv run mypy tms_mcp # Type check
uv run pre-commit run --all-files # Run all hooks
Running the Server
uv run python -m tms_mcp.main # Start server (stdio)
uv run python -m tms_mcp.main update-docs # Update all provider docs
uv run python -m tms_mcp.main update-docs omelet # Update specific provider
Code Style Guidelines
Python Version & Type Hints
- Python 3.11+ required
- Use native collection types for type hints:
# CORRECT def process(items: list[str], config: dict[str, Any]) -> tuple[int, str]: ... def fetch(url: str | None = None) -> dict[str, Any] | None: ... # WRONG - Do NOT use typing module equivalents from typing import List, Dict, Optional # NO! - Use
Annotated[type, "description"]for MCP tool parameters
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 · 166 lines · 1,535 tokens per session scan A 43e2322d5215
tms-dev-mcp AGENTS.md is an instructions file published in the GitHub repository omelet-ai/tms-dev-mcp (2 stars, last pushed 17d ago), licensed MIT. It adds 1,535 tokens to every session, about $0.0077 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.
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 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).
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.