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/php-workx/modal-mcp/agents-mdgit clone --depth 1 https://github.com/php-workx/modal-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.00385 | $0.00385 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
modal-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 yesterday.
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.
What it actually says
AGENTS.md
AGENTS.md is the durable instruction file for this repo.
What This Repo Is
modal-mcp is a local, read-oriented MCP server for inspecting Modal state.
The core product boundary is that credentials stay local and the default tool
surface is read-only.
Hard Rules
- Preserve the read-only default posture unless a task explicitly asks for mutating behavior.
- Never check real Modal credentials or secrets into the repo.
- Prefer the repo’s
uv-managed Python environment over ambient Python. - Keep local-file secret handling and
.env-driven setup intact. - Never merge pull requests or create releases without explicit user approval. Agents may prepare, review, and push changes, but the human must trigger merges, releases, and any action that modifies the default branch.
Common Commands
uv sync --extra dev
uv run pytest
uv run ruff check .
uv run modal-mcp doctor --env-file .env
uv run modal-mcp run --env-file .env
Optional stricter checks if needed:
uv run mypy src
uv run pip-audit
Common Workflows
1. Server or tool changes
- Run tests and lint through
uv. - Preserve the read-oriented tool contract unless the task explicitly changes that product decision.
- Keep setup and doctor flows working for local users.
2. Credential or setup changes
- Do not replace file-based secret handling with checked-in secrets.
- Keep
.envand.secrets/semantics local-only. - If setup behavior changes, update the README examples too.
References
README.md— product boundaries and setup flowpyproject.toml— runtime and dev-tool entry points
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.
- yesterday First seen · 58 lines · 385 tokens per session scan A 2852eee99770
modal-mcp AGENTS.md is an instructions file published in the GitHub repository php-workx/modal-mcp (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 385 tokens to every session, about $0.0019 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
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.
buildNext
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).
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.
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).
spec-kit 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
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.