Borrowing it
Nothing to install: this file belongs to AceDataCloud/VeoMCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AceDataCloud/VeoMCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/AceDataCloud/VeoMCPWrote 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/acedatacloud/veomcp/claude-md)<a href="https://agentmods.dev/instructions/acedatacloud/veomcp/claude-md"><img src="https://agentmods.dev/badge/instructions/acedatacloud/veomcp/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.1 | $0.00398 | $0.00398 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
VeoMCP 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 6d 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.
This is a copy
84% identical to SeedanceMCP CLAUDE.md — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
VeoMCP
MCP (Model Context Protocol) server for Veo (Google) AI video generation via AceDataCloud API.
Project Structure
core/
config.py — Settings dataclass (API token, base URL)
server.py — FastMCP server singleton
client.py — httpx async HTTP client
types.py — Literal types (VeoModel, etc.)
exceptions.py — Error classes (AuthError, APIError, TimeoutError)
utils.py — Formatting helpers
tools/
video_tools.py — generate video from text or image
task_tools.py — query task status, batch query
info_tools.py — list models, actions
prompts/ — LLM guidance prompts
tests/ — pytest-asyncio + respx tests
Sync from Docs
When invoked by the sync workflow, the Docs repo is checked out at _docs/. Your job:
- Source of truth —
_docs/openapi/veo.jsonis the OpenAPI spec for the VeoMCP API. - Compare models — The Literal types in
core/types.pymust match the spec's model enum. Add/remove as needed. - Compare parameters — Each
@mcp.tool()function's parameters should match the corresponding OpenAPI endpoint. - Update defaults — If a new model becomes the recommended default, update the default in
core/types.py. - Update README — Keep the model table and feature list current.
- Add tests — For new tools or parameters, add test cases in
tests/. - PR title — Use format:
sync: <description> [auto-sync]
Development
pip install -e ".[dev]"
pytest --cov=core --cov=tools
ruff check .
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.
- 6d ago First seen · 42 lines · 398 tokens per session scan A 9053d2b069f3
VeoMCP CLAUDE.md is an instructions file published in the GitHub repository AceDataCloud/VeoMCP (3 stars, last pushed 9d ago), licensed MIT. It adds 398 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to SeedanceMCP CLAUDE.md, differing in 8 lines, and is treated as a copy.
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).
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.
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.