Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Grinv/steam-games-mcp --skill docs-consistency-checkgit clone --depth 1 https://github.com/Grinv/steam-games-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/steam-games-mcp/docs-consistency-check)<a href="https://agentmods.dev/skills/grinv/steam-games-mcp/docs-consistency-check"><img src="https://agentmods.dev/badge/skills/grinv/steam-games-mcp/docs-consistency-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/steam-games-mcp/docs-consistency-check"><img src="https://agentmods.dev/badge/skills/grinv/steam-games-mcp/docs-consistency-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.00056 | $0.00774 |
| Opus 5 | $0.00028 | $0.00387 |
| Sonnet 5 | $0.00011 | $0.00155 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
docs-consistency-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
Docs/metadata consistency
Check every one of these, not just a sample:
README.md's tool table matchessrc/server.ts's registrations (names, and the keyless-vs-key-gated column against each tool's actual behavior).manifest.json's andserver.json'stoolsarrays list the same tool names as what's actually registered (npm test'se2e.test.tsalready asserts this — treat a failure there as authoritative). Theirdescriptionfields are deliberately short, independent marketing-style summaries, NOT a copy of the tool's full.describe()/descriptiontext insrc/tools/*.ts— don't "fix" them to match verbatim, that's not a bug. Do re-read them for accuracy if a tool's behavior changed in a way the short summary now misrepresents.- Tool
description/field.describe()text insrc/tools/*.tsitself: does it still match the actualinputSchema/outputSchemaand the real behavior? Cross-check new/edited descriptions against thetool-description-checkskill (Glama's TDQS rubric) per AGENTS.md. Check eachoutputSchemabranch against what the shaper actually builds, not just the happy path —get_owned_games'found:falsebranch still advertised anownsfield the 0.10.1 fix had stopped emitting, i.e. the published schema re-legitimized the very bug that was fixed. CHANGELOG.md's[Unreleased]section (see thechangelog-styleskill for entry style) has one line per real behavior change made in this pass — add missing entries, don't just flag them as missing.AGENTS.md's "Keyless caveat" list and itssrc/tree (and this.agents/skills/entry) still match the filesystem and the actual keyless method list.docs/notes.md,docs/clients.mdand any otherdocs/*.mdfor stale phrasing (e.g. describing something as "once published"/"upcoming" that already shipped).PRIVACY.mdandSECURITY.md: re-verify every specific claim against the actual current code, don't just skim for plausibility — which credentials exist and how each is transmitted/redacted, what is and isn't cached (incl. cache key/TTL), the current list of read-only vs. write/mutating tools, and any host-allowlist statement. This class of drift is easy to miss because it reads fine on its own and only breaks against the code: this repo's ownSECURITY.md/PRIVACY.mdboth claimed "player-specific data is never cached" after a later feature (get_player_summary's Steam-level cache) added exactly that, and a separate claim conflated an actually-cached field ("review histogram") with a similarly-named never-cached one ("reviews") — neither doc was self-evidently wrong, both required re-reading the client code to catch.
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 · 49 lines · 56 tokens per session scan A 762492f33256
docs-consistency-check is a skill published in the GitHub repository Grinv/steam-games-mcp (4 stars, last pushed 16d ago), licensed MIT. It adds 56 tokens to every session and 774 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
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
b123d-modeling
Use this skill when asked to model, build, or modify a 3D part or assembly with build123d — from a text description, a technical drawing (image or PDF), dimensions in a spec, or an existing STEP/STL file.
research
Answer a hard, open-ended question about how the project works or is built by synthesizing every source — code, structure, git history, prior decisions, discussion, caveats — and verifying each claim against the source. Use for deep cross-cutting questions that span more than one area. Narrower siblings — a single…
doc-gaps
Find what's underdocumented or hard to retrieve in a project — the topics people search for but don't find. Use when improving docs or the wiki, or when asked what's missing or poorly covered.
che-word-mcp
A Swift-native MCP server for Microsoft Word (.docx) document manipulation. Provides 83 tools for reading, writing, and modifying Word documents without requiring Microsoft Word installation.
himalayas-employer
AI hiring assistant for Himalayas. Post remote jobs, manage company profiles, source talent, message candidates, and benchmark salaries using the Himalayas MCP server.