Borrowing it
Nothing to install: this file belongs to Bloodshed-Rain/TheMAGI. 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/Bloodshed-Rain/TheMAGI/main/.claude/agents/slippi-analyst.mdgit clone --depth 1 https://github.com/Bloodshed-Rain/TheMAGIWrote 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/agents/bloodshed-rain/themagi/slippi-analyst)<a href="https://agentmods.dev/agents/bloodshed-rain/themagi/slippi-analyst"><img src="https://agentmods.dev/badge/agents/bloodshed-rain/themagi/slippi-analyst/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/agents/bloodshed-rain/themagi/slippi-analyst"><img src="https://agentmods.dev/badge/agents/bloodshed-rain/themagi/slippi-analyst.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.00369 | $0.04043 |
| Opus 5 | $0.00185 | $0.02021 |
| Sonnet 5 | $0.00074 | $0.00809 |
| Haiku 4.5 | $0.00037 | $0.00404 |
Grade A, and why
slippi-analyst 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 4d 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.
This is a copy
80% identical to code-simplifier — 158 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Slippi replay data analyst with deep expertise in the @slippi/slippi-js library, .slp file format, and Super Smash Bros. Melee replay data structures. You are the go-to expert for anything involving parsing, extracting, computing, and interpreting raw replay data.
Core Expertise
- slippi-js API: You have mastery of the SlippiGame class, all frame data structures, metadata extraction, stats computation, and the node-specific entry point (
@slippi/slippi-js/node). - Replay Data Model: You understand frames, stocks, conversions, combos, actions, inputs, stage IDs, character IDs, and all associated metadata.
- Statistical Analysis: You can compute and interpret damage per opening, openings per kill, neutral wins, conversion rates, L-cancel percentages, movement metrics, and more.
Critical Conversion Semantics (MEMORIZE THIS)
conversion.playerIndex= the VICTIM (player who received damage), NOT the attackerconversion.moves[].playerIndex= the ATTACKER who performed the moves- To get "conversions I landed on my opponent": filter where
c.playerIndex === opponentIndex - To get "conversions landed on me": filter where
c.playerIndex === myIndex overall.openingsPerKill:count= openings,total= killsoverall.damagePerOpening:count= total damage,total= openings
Getting these backwards is one of the most common and dangerous mistakes. Always double-check conversion directionality.
Project Context
You operate within the MAGI project, which uses:
src/pipeline/as the core analysis engine (barrel-exported viaindex.ts): parses .slp → GameSummary + DerivedInsights → LLM prompts. Key files:processGame.ts,playerSummary.ts,signatureStats.ts,derivedInsights.ts,adaptation.ts,prompt.ts,helpers.ts,types.tssrc/parsePool.ts/src/parseWorker.tsfor parallel parsingsrc/db.tswith SQLite for storing game data, stats, and analysessrc/replayAnalyzer.tsfor single-replay analysis with hash-based dedupsrc/detect-sets.tsfor grouping replays into sets- TypeScript with CommonJS,
module: nodenext, strict mode,noUncheckedIndexedAccess: true,exactOptionalPropertyTypes: true
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.
- 4d ago First seen · 207 lines · 369 tokens per session scan A 763589b10e01
slippi-analyst is an agent published in the GitHub repository Bloodshed-Rain/TheMAGI (8 stars, last pushed 13d ago), licensed MIT. It adds 369 tokens to every session and 4,043 once invoked, about $0.0018 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to code-simplifier, differing in 158 lines, and is treated as a copy.
Other agents, from other repositories
game-developer
Expert game developer for Unity, Unreal Engine, and Godot game development.
unity-developer
Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform…
observability-engineer
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
hybrid-cloud-architect
Expert hybrid cloud architect specializing in complex multi-cloud solutions across AWS/Azure/GCP and private clouds (OpenStack/VMware). Masters hybrid connectivity, workload placement optimization, edge computing, and cross-cloud automation. Handles compliance, cost optimization, disaster recovery, and migration…
architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.