Borrowing it
Nothing to install: this file belongs to kud/mcp-gtv. 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/kud/mcp-gtv/main/CLAUDE.mdgit clone --depth 1 https://github.com/kud/mcp-gtvWrote 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/kud/mcp-gtv/claude-md)<a href="https://agentmods.dev/instructions/kud/mcp-gtv/claude-md"><img src="https://agentmods.dev/badge/instructions/kud/mcp-gtv/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.00399 | $0.00399 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
mcp-gtv 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.
What it actually says
mcp-gtv
MCP server exposing Google TV control to MCP clients. Thin wrapper over
@kud/gtv — part of the ecosystem
@kud/androidtv-remote ← @kud/gtv ← (mcp-gtv | gtv-cli).
How it connects
No API, no token. It reads already-paired devices from the shared config store
at ~/.config/gtv/config.json (devices are paired via the gtv CLI). All
control tools act on the current device; gtv_set_device switches it.
A single warm createSession is held for the life of the server (connect once,
reuse). This removes the per-call TLS handshake and keeps state live, so every
control tool returns the TV's resulting state (powered, foreground app, volume)
as feedback for the model.
Tools
gtv_list_devices— list paired devices, marking the current onegtv_set_device— select the current device by host or name (resets the session)gtv_get_state— read live state: connected, powered, foreground app, volumegtv_send_key— send a remote key (names from@kud/gtv'sKEYS); returns stategtv_type_text— type text via IME into the focused field; returns stategtv_launch_app— launch an app by catalog name/id or URI; waits for + returns the new app
Conventions
ESM-only, functional (no classes), exact version pins, tsup build, stdio
transport. Releases are tag-driven via OIDC (git tag vX.Y.Z && git push --tags)
— never npm publish by hand.
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 · 32 lines · 399 tokens per session scan A 8aa44cd2f813
mcp-gtv CLAUDE.md is an instructions file published in the GitHub repository kud/mcp-gtv (0 stars, last pushed 2mo ago), licensed MIT. It adds 399 tokens to every session, about $0.0020 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).
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.
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
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.