Borrowing it
Nothing to install: this file belongs to AceDataCloud/FishMCP. 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/FishMCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/AceDataCloud/FishMCPWrote 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/fishmcp/claude-md)<a href="https://agentmods.dev/instructions/acedatacloud/fishmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/acedatacloud/fishmcp/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.00540 | $0.00540 |
| Opus 5 | $0.00270 | $0.00270 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
FishMCP 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FishMCP
MCP (Model Context Protocol) server for the AceDataCloud Fish Audio API — text-to-speech with voice conditioning powered by Fish Audio models.
Project Structure
core/
config.py — Settings dataclass (API token, base URL, timeouts)
server.py — FastMCP server singleton + optional OAuth provider
client.py — FishClient: async httpx wrapper for /fish/* endpoints
types.py — Literal types (FishModel, etc.)
exceptions.py — Error classes (FishAuthError, FishAPIError, FishTimeoutError)
oauth.py — Generic AceDataCloud OAuth 2.1 provider (PKCE)
tools/
audio_tools.py — fish_generate_audio (submit a TTS task)
task_tools.py — fish_get_task, fish_get_tasks_batch
info_tools.py — fish_list_models, fish_get_model, fish_get_usage_guide
prompts/
__init__.py — fish_guide, fish_workflow_examples
tests/
test_smoke.py — Smoke tests (settings, server import, tool registration)
TTS workflow
- Pick a voice model (
fish_list_models→fish_get_model). - Submit text (
fish_generate_audio(text=..., model="s2-pro", reference_id=...)). - Poll status until terminal (
fish_get_task(task_id=...)). - Read the final
audio_urlfrom the task payload and play / download it.
Sync from Docs
When invoked by the sync workflow, the Docs repo is checked out at _docs/. Your job:
- Source of truth —
_docs/openapi/fish.jsonis the OpenAPI spec for the Fish Audio API. - Compare models — The Literal types in
core/types.pymust match the spec's voice 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]
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 · 52 lines · 540 tokens per session scan A 3abc91854e4c
FishMCP CLAUDE.md is an instructions file published in the GitHub repository AceDataCloud/FishMCP (1 stars, last pushed today), licensed MIT. It adds 540 tokens to every session, about $0.0027 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.
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).
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.
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.