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/prompt-check/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/prompt-check)<a href="https://agentmods.dev/skills/grinv/tmdb-mcp/prompt-check"><img src="https://agentmods.dev/badge/skills/grinv/tmdb-mcp/prompt-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/grinv/tmdb-mcp/prompt-check"><img src="https://agentmods.dev/badge/skills/grinv/tmdb-mcp/prompt-check.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.00419 |
| Opus 5 | $0.00029 | $0.00210 |
| Sonnet 5 | $0.00012 | $0.00084 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
prompt-check 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 9d 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
Prompt check — live-test every MCP Prompt argument combination
A static read comparing prompt text against tool names/params misses argument-handling bugs (found this way in a sibling repo: a prompt silently dropped one of two independent optional filters whenever it was given without the other, because its branching logic wrongly required both together). Actually render every prompt through the real MCP protocol:
npx @modelcontextprotocol/inspector --cli node dist/index.js --method prompts/list
npx @modelcontextprotocol/inspector --cli node dist/index.js --method prompts/get \
--prompt-name <name> --prompt-args key=value key2=value2
--prompt-args takes space-separated key=value pairs, not a JSON blob
— the CLI rejects JSON with "Invalid parameter format".
For each prompt: no args, only one optional arg at a time, and all of them together — an arg that's individually optional can still break when given alone.
For an enum-valued arg (e.g. media_type: "movie" | "tv"), render
every value, not just one — each can take a genuinely different branch
in the prompt's own step-building logic. Missing this exact gap is how a
real bug got past a prior live-audit pass in this repo: media_type=movie
rendered fine, but media_type=tv left a dangling reference to a step ("the
equivalent movies filter") that only exists in the movies branch — caught
later by a /code-review pass, not by live-audit, because only one enum
value had actually been rendered here.
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.
- 9d ago First seen · 35 lines · 58 tokens per session scan A 8eebe57c69b5
prompt-check is a skill published in the GitHub repository Grinv/tmdb-mcp (4 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 419 once invoked, about $0.0003 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 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.