Borrowing it
Nothing to install: this file belongs to Grinv/anilist-mcp-server. 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/anilist-mcp-server/main/.agents/skills/live-audit/SKILL.mdgit clone --depth 1 https://github.com/Grinv/anilist-mcp-serverWrote 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/anilist-mcp-server/live-audit)<a href="https://agentmods.dev/skills/grinv/anilist-mcp-server/live-audit"><img src="https://agentmods.dev/badge/skills/grinv/anilist-mcp-server/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/anilist-mcp-server/live-audit"><img src="https://agentmods.dev/badge/skills/grinv/anilist-mcp-server/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.00085 | $0.05004 |
| Opus 5 | $0.00043 | $0.02502 |
| Sonnet 5 | $0.00017 | $0.01001 |
| Haiku 4.5 | $0.00009 | $0.00500 |
Grade A, and why
live-audit scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
type's equivalent root lookup — confirmed live (raw `curl`, no auth) that How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
live-audit — anilist-mcp-server 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 anilist-mcp-server
package, hunt for bugs/edge cases, or repeat "the same kind of testing as
before." Sibling repos (tmdb-mcp, mal-mcp, steam-games-mcp) 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
AniList API) 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, requireAuth() placement, outputSchema precision,
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__anilist__* tools in Claude Code). If it isn't
connected, connect it first rather than skipping straight to step 1.
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
0. Confirm "published"/"fixed" actually means what you think it means
node -p "require('./package.json').version"; npm view anilist-mcp-server version; git log --oneline -5
If package.json's version matches the npm-published version, live-testing
the running tools is testing the published package. If you've since made
local fixes, remember the running MCP server is a separate process from
your edits — stdio servers don't hot-reload. Ask for a restart before
trusting a live call against fixed code, and state plainly whether findings
apply to the published package or to fixed-but-unreleased/unrestarted code.
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.
- 8d ago First seen · 336 lines · 85 tokens per session scan A e0a1bf920a0c
live-audit is a skill published in the GitHub repository Grinv/anilist-mcp-server (1 stars, last pushed 15d ago), licensed MIT. It adds 85 tokens to every session and 5,004 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.