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.
git clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokensWrote 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/commands/madebytokens/claude-code-plugins-madebytokens/analyze)<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/analyze"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/analyze.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.00013 | $0.01165 |
| Opus 5 | $0.00006 | $0.00583 |
| Sonnet 5 | $0.00003 | $0.00233 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
analyze 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 7d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chess Analyze Command
Perform detailed post-game analysis to identify critical moments, mistakes, missed opportunities, and lessons for improvement.
Prerequisites
This command works best after a completed game, but can also analyze:
- An ongoing game (analysis of moves so far)
- A position from a FEN string
- A game from PGN notation
Step 1: Load Game Data
Read the game state and log:
Read: state/game.json
Read: state/game.log
If analyzing a specific position or PGN provided by user, parse that instead.
Step 2: Identify Key Moments
Review the game and identify:
Critical Positions
Positions where the evaluation changed significantly:
- Turning points (advantage shifted)
- Missed wins (we had a winning move but didn't play it)
- Blunders (moves that threw away advantage)
- Brilliant moves (unexpected strong moves)
Tactical Moments
- Forks, pins, skewers that occurred or were missed
- Sacrifices (sound or unsound)
- Checkmate threats
Strategic Themes
- Pawn structure evolution
- Piece activity changes
- King safety considerations
- Control of key squares/files
Step 3: Move-by-Move Review
For each move in the game, provide:
Move [N]: [UCI] ([SAN])
Our Assessment: [What we thought]
Actual Quality: [Excellent/Good/OK/Inaccuracy/Mistake/Blunder]
Better Alternative: [if applicable]
Comment: [Brief explanation]
Focus on:
- Moves where we went wrong
- Moves where we missed something better
- Moves that were particularly good
Don't analyze every move in detail - focus on the interesting ones.
Step 4: Phase Analysis
Opening
- Did we follow opening principles?
- How did our opening choice work out?
- Where did we deviate from theory (if applicable)?
- What was the resulting position?
Middlegame
- What was our plan?
- Did we execute it well?
- Key tactical moments
- Piece coordination
Endgame (if reached)
- Technique evaluation
- Missed wins or draws
- Time management (if timed game)
Step 5: Summary 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.
- 7d ago First seen · 198 lines · 13 tokens per session scan A 7d9597774185
analyze is a command published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 1,165 once invoked, about $0.0001 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 commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
status
Show 3d-design team status and recent activity.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.