Borrowing it
Nothing to install: this file belongs to that-lucas/tts-mcp. 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/that-lucas/tts-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/that-lucas/tts-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/that-lucas/tts-mcp/agents-md)<a href="https://agentmods.dev/instructions/that-lucas/tts-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/that-lucas/tts-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.01109 | $0.01109 |
| Opus 5 | $0.00554 | $0.00554 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
tts-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 8d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents operating in this repository.
Repository Overview
- Project:
tts-mcp - Language: Python 3.11+
- Packaging: Hatchling (
pyproject.toml) - Source root:
src/tts_mcp/ - Tests root:
tests/ - Runtime modes: MCP server (
tts-mcp) + CLIs (tts-speak,tts-voices,tts-batch)
Key Modules
src/tts_mcp/server.py- MCP entrypoint and tool registrationsrc/tts_mcp/speak.py- local synthesis CLIsrc/tts_mcp/list_voices.py- voice listing CLIsrc/tts_mcp/batch.py- multi-voice generation CLIsrc/tts_mcp/core/auth.py- Google ADC client creationsrc/tts_mcp/core/profile.py- profile resolution/load/playbacksrc/tts_mcp/core/synth.py- synthesis helpers and request/result modelssrc/tts_mcp/core/voices.py- voice filteringsrc/tts_mcp/core/usage.py- usage/cost snapshot logicREADME.mdandCONTRIBUTING.md- user/developer docs
Canonical Dev Commands
Use Make targets first:
make setup
make test
make lint
make lint-fix
What they do:
make setup: create.venv, install editable package + dev deps, set git hooksmake test: run pytest via.venv/bin/python -m pytestmake lint: runruff check --output-format=concise .andruff format --check .make lint-fix: auto-fix lint issues and apply formatting
Code Style Guidelines
Imports
- Group and sort imports: stdlib, third-party, local
- Follow Ruff isort behavior; do not hand-format against it
- No wildcard imports; remove unused imports
Formatting
- Line length is 120
- Use double quotes (Ruff formatter default)
- Let Ruff handle spacing/wrapping
Types
- Prefer explicit type annotations for params and returns
- Keep
from __future__ import annotations(existing project pattern) - Use built-in generics (
list[str],dict[str, Any], etc.) - Use dataclasses for structured transfer objects
Naming
snake_case: functions, vars, modulesPascalCase: classes/dataclassesUPPER_SNAKE_CASE: constants- Tests named
test_<behavior>
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.
- 8d ago First seen · 124 lines · 1,109 tokens per session scan A be2e2d2a1903
tts-mcp AGENTS.md is an instructions file published in the GitHub repository that-lucas/tts-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 1,109 tokens to every session, about $0.0055 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
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.