Borrowing it
Nothing to install: this file belongs to Grinv/tmdb-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/Grinv/tmdb-mcp/main/.agents/skills/live-audit/SKILL.mdgit clone --depth 1 https://github.com/Grinv/tmdb-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/skills/grinv/tmdb-mcp/live-audit)<a href="https://agentmods.dev/skills/grinv/tmdb-mcp/live-audit"><img src="https://agentmods.dev/badge/skills/grinv/tmdb-mcp/live-audit.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.00000 | $0.03038 |
| Opus 5 | $0.00000 | $0.01519 |
| Sonnet 5 | $0.00000 | $0.00608 |
| Haiku 4.5 | $0.00000 | $0.00304 |
Grade A, and why
live-audit 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 7d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
live-audit — tmdb-mcp health check + edge-case hunt
Repo-specific playbook, for any agent/model working on this repo (not tied to
a particular harness — see AGENTS.md's own framing). Use it when asked to
test/audit/smoke-test the published tmdb-mcp package, hunt for bugs or edge
cases, or repeat "the same kind of testing as before."
Goal: find real bugs/inaccuracies in the currently published tmdb-mcp
package (not just "does it build") by actually calling its live MCP tools the
way a downstream agent would, then fixing what's found. Read AGENTS.md first
if it's not already in context — every fix and every CHANGELOG entry must
follow its conventions (.strict() schemas, shaper/schema 1:1, description
style, commit author/no-Co-Authored-By, etc.).
This assumes the server is already reachable as an MCP connection in your
current session (however your harness exposes that — e.g. as mcp__tmdb__*
tools in Claude Code). If it isn't connected, connect it first (see
README.md's client-setup section) rather than skipping straight to step 1.
Hard rule — do not skip ahead: if your harness has a task/todo tool, create
one task per numbered step below (0-5) plus one per bullet under step 2's
checklist and step 3's list, before doing anything else, and mark each
complete only when actually done. The failure mode this guards against is
real: finding a bug mid-step-2 and immediately jumping to fix it, leaving
step 3 (docs/metadata consistency) half-done and unreported. Step 3 is not
optional polish — a real fix from step 2 routinely has stale echoes
elsewhere (a tool's own .describe() text repeating an old constant,
manifest.json's hand-maintained tools/prompts copy per
docs/releasing.md, a comment in docs/*.md) that step 2 alone will never
surface. A fix isn't done until every one of its echoes is updated too —
finish step 3 in full before step 4's report, every single time.
0. Confirm "published" actually means HEAD
node -p "require('./package.json').version"; npm view tmdb-mcp version; git log --oneline -5
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.
- 7d ago First seen · 207 lines · 0 tokens per session scan A 61addfadf910
live-audit is a skill published in the GitHub repository Grinv/tmdb-mcp (4 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,038 tokens. 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 skills, from other repositories
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
prompt-check
Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.
tool-description-check
Self-check a new or edited MCP tool description/field .describe() text before committing — verify every behavioral claim against live testing or source, check for contradictions with sibling tools, and score against Glama's Tool Definition Quality Score (TDQS) rubric. Use whenever a tool description or schema field…
release
Cut a release of steam-games-mcp — draft CHANGELOG entries, check docs/metadata consistency, then bump/tag/push. Use when asked to release, cut a version, or publish a new version of this package.
docs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
verify-cli
Run smoke tests against the mpak CLI to verify all commands work correctly before publishing a new release.