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 live-auditgit 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/live-audit)<a href="https://agentmods.dev/skills/grinv/steam-games-mcp/live-audit"><img src="https://agentmods.dev/badge/skills/grinv/steam-games-mcp/live-audit/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/live-audit"><img src="https://agentmods.dev/badge/skills/grinv/steam-games-mcp/live-audit.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.00083 | $0.06384 |
| Opus 5 | $0.00042 | $0.03192 |
| Sonnet 5 | $0.00017 | $0.01277 |
| Haiku 4.5 | $0.00008 | $0.00638 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
live-audit — steam-games-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 agent-agnostic framing). Use it
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 before."
Sibling repos (tmdb-mcp, mal-mcp, anilist-mcp-server) keep their own
live-audit/SKILL.md — when either this file or a sibling's improves, sync
the useful parts both ways rather than letting them drift.
Goal: find real bugs/inaccuracies in the live tool behavior (against the real
Steam Storefront + Web APIs) and in the source, then fix what's found. Read
AGENTS.md first if it's not already in context — every fix must follow its
conventions (guard()/never-throw, schema-first format/*.schemas.ts,
keyless-vs-keyed tool gating, commit author/no-Co-Authored-By, etc.).
This assumes the server is already reachable as an MCP connection in your
current session (e.g. as mcp__steam__* tools in Claude Code). If it isn't
connected, connect it first rather than skipping straight to step 1.
Unlike the anilist/mal siblings, this server has no OAuth login and no
mutation tools — every tool is a read against public Steam data. The
per-call risk here isn't "did I just modify a real account," it's "did I just
call a key-gated tool without a key," "did I treat a private profile's
default response as a bug," or "did I burn a real person's SteamID64 in a
committed test fixture." Read ## 2 before live-calling anything.
Contents
-
- Confirm "published"/"fixed" actually means what you think it means
-
- Static pass first (cheap, catches regressions before you burn API calls)
-
- Safety rules for live testing (read before calling anything)
-
- Live edge-case sweep
-
- Source-level code review
-
- Docs/metadata consistency
-
- Report, then fix only what's confirmed
-
- Commit + changelog, if asked
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 · 411 lines · 83 tokens per session scan A 77df07822938
live-audit is a skill published in the GitHub repository Grinv/steam-games-mcp (4 stars, last pushed 16d ago), licensed MIT. It adds 83 tokens to every session and 6,384 once invoked, about $0.0004 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
impl-validator
Validate whether an implementation matches its stated goal. Use this skill when a skill or agent wants a second opinion on its own output, when the user says "check this implementation", "validate what you did", "is this correct?", "review the output", or "did you do this right?". Also spawned automatically as a…
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.
omh-verification-gate
This is a Hermes-native verification-gate workflow skill.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
pre-ship-review
Run a structured quality review before shipping code at any checkpoint such as PRs, releases, or milestones. Use whenever the user says.
review
Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".