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/thestreamcode/chutes-media-mcp/agents-mdgit clone --depth 1 https://github.com/TheStreamCode/chutes-media-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/thestreamcode/chutes-media-mcp/agents-md)<a href="https://agentmods.dev/instructions/thestreamcode/chutes-media-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/thestreamcode/chutes-media-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.03650 | $0.03650 |
| Opus 5 | $0.01825 | $0.01825 |
| Sonnet 5 | $0.00730 | $0.00730 |
| Haiku 4.5 | $0.00365 | $0.00365 |
Grade A, and why
chutes-media-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 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.
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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working on chutes-media-mcp
Operating guide for AI coding agents and new contributors. It describes this repository only. Read it before changing anything; the rules below encode decisions that were made deliberately and that are easy to undo by accident.
What this project is
chutes-media-mcp is a published npm package that lets a coding agent generate image, video,
music and speech through Chutes and save the asset straight into the user's
project. It ships three surfaces from one codebase:
- an MCP server (
chutes-media-mcpbin, stdio transport) — the primary interface, - a thin CLI (
chutes-mediabin) — fallback for shells and agents without MCP, - a bundled Agent Skill (
skill/chutes-media/) documenting the describe→generate workflow.
Repository: https://github.com/TheStreamCode/chutes-media-mcp · public, MIT. Registry: https://www.npmjs.com/package/chutes-media-mcp.
Stack and runtime
- TypeScript (strict, ESM only), bundled with tsup (esbuild),
target: node20. - Runtime for the published artifact: Node.js ≥ 20.3 (
engines.node). Do not raise this without a major version bump — it is a breaking change for installed users. - Development toolchain needs Node.js
^20.19.0,≥ 22.13.0, or≥ 24. CI runs the matrix 20 / 22 / 24 onubuntu-latest. - Package manager: npm, with
package-lock.json. Never introduce pnpm, yarn or bun, never add a second lockfile, and never hand-editpackage-lock.json— change it only through npm commands. - Runtime dependencies are deliberately minimal:
@modelcontextprotocol/sdk,ajv,zod. Prefer native Node APIs (globalfetch,node:utilparseArgs,node:crypto) over new dependencies.
Architecture
src/
├── core/ # transport-agnostic; knows nothing about MCP or the CLI
│ ├── chutes-client.ts # HTTP: list / describe / warmup / invoke / download, auth, URL safety, error mapping
│ ├── media-engine.ts # validate → resolve input assets → warmup → invoke (retry) → save → provenance
│ ├── schema-validate.ts # Ajv validation of params against the live cord JSON Schema
│ ├── present.ts # shared describe/list/error formatting, reused by both frontends
│ ├── config.ts # environment → ChutesConfig
│ └── types.ts # shared types
├── mcp/server.ts # MCP stdio server — registers the 3 tools, delegates to core
├── cli/index.ts # CLI — same operations via util.parseArgs
└── index.ts # public exports of the core
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 · 248 lines · 3,650 tokens per session scan A dcaca666a4dd
chutes-media-mcp AGENTS.md is an instructions file published in the GitHub repository TheStreamCode/chutes-media-mcp (1 stars, last pushed 14d ago), licensed MIT. It adds 3,650 tokens to every session, about $0.0182 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
NanoBananaMCP CLAUDE.md
Claude Code instructions for AceDataCloud/NanoBananaMCP, covering nanobananamcp, project structure, sync from docs and development.
agnes-image-mcp AGENTS.md
AGENTS.md instructions for hskelp9527-pixel/agnes-image-mcp, covering agnes-image-mcp, 这个项目的边界, 结构, 改代码的规矩 and 验证.
NanoBananaMCP copilot-instructions.md
Copilot instructions for AceDataCloud/NanoBananaMCP, covering copilot instructions for nanobananamcp, sync from docs, project structure and development.
FluxMCP CLAUDE.md
Claude Code instructions for AceDataCloud/FluxMCP, covering fluxmcp, project structure, sync from docs and development.
SeedreamMCP copilot-instructions.md
Copilot instructions for AceDataCloud/SeedreamMCP, covering copilot instructions for seedreammcp, sync from docs, project structure and development.
SeedreamMCP CLAUDE.md
Claude Code instructions for AceDataCloud/SeedreamMCP, covering seedreammcp, project structure, sync from docs and development.