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 agentmods add skills/grinv/mal-mcp/live-auditnpx skills add Grinv/mal-mcp --skill live-auditgit clone --depth 1 https://github.com/Grinv/mal-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/mal-mcp/live-audit)<a href="https://agentmods.dev/skills/grinv/mal-mcp/live-audit"><img src="https://agentmods.dev/badge/skills/grinv/mal-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.00081 | $0.06108 |
| Opus 5 | $0.00041 | $0.03054 |
| Sonnet 5 | $0.00016 | $0.01222 |
| Haiku 4.5 | $0.00008 | $0.00611 |
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 5d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
live-audit — mal-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 mal-mcp package, hunt
for bugs/edge cases, or repeat "the same kind of testing as before." Sibling
repos (tmdb-mcp, steam-games-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
Tenrai API, its official-MAL-API fallback, and the official MAL API itself)
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, format.schemas.ts's .strict() shaper/schema 1:1 rule vs.
clients/mal.ts's deliberate z.looseObject(), 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__mal__* tools in Claude Code). If it isn't
connected, connect it first rather than skipping straight to step 1.
Contents
- How to run this: fan the sections out, don't walk them inline
-
- 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
How to run this: fan the sections out, don't walk them inline
Split the sections below across concurrent subagents and run them in parallel. Walking this file top to bottom in one thread is the wrong default: the sections touch independent surfaces, so serial execution wastes wall-clock and burns the main thread's context on file dumps it only needs a conclusion from. If your environment has no concurrency primitive, run inline and say so in the report.
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.
- 5d ago First seen · 414 lines · 81 tokens per session scan A d527676f111c
live-audit is a skill published in the GitHub repository Grinv/mal-mcp (2 stars, last pushed 12d ago), licensed MIT. It adds 81 tokens to every session and 6,108 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
live-audit
Audit anilist-mcp-server — build/test/lint gate, live MCP tool edge-case sweep (input validation, not-found paths, mutations with capture/revert), source-level code review, and docs/metadata consistency. Use when asked to test/audit the published or just-fixed anilist-mcp-server package, hunt for bugs/edge cases, or…
tool-description-check
Self-check a new or edited MCP tool description/field .describe() text before committing — verify every behavioral claim against live testing, 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 description…
release
Cut a release of anilist-mcp-server — 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.
fixture-accuracy-check
Make sure a mocked-fetch test fixture mirrors AniList's real GraphQL response shape, not just whatever fields make the current code pass. Use before writing or changing a fixture in src/tests/.test.ts.
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.
mutation-test-safety
The capture-state/smallest-change/verify/revert/verify-revert contract for live-testing a mutation tool against a real account. Use any time you're about to call a mutation tool live, not just during a full audit.