Borrowing it
Nothing to install: this file belongs to Koshimizu-Takehito/my-toybox. 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/Koshimizu-Takehito/my-toybox/develop/.claude/commands/README.mdgit clone --depth 1 https://github.com/Koshimizu-Takehito/my-toyboxWrote 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/koshimizu-takehito/my-toybox/readme)<a href="https://agentmods.dev/commands/koshimizu-takehito/my-toybox/readme"><img src="https://agentmods.dev/badge/commands/koshimizu-takehito/my-toybox/readme/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/commands/koshimizu-takehito/my-toybox/readme"><img src="https://agentmods.dev/badge/commands/koshimizu-takehito/my-toybox/readme.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.00000 | $0.01694 |
| Opus 5 | $0.00000 | $0.00847 |
| Sonnet 5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
README 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 6d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MyToybox Claude Code Commands
Custom slash commands for efficient MyToybox development workflows.
Available Commands
| Command | Description | Agent Role |
|---|---|---|
/new-screen |
Create a new visual effects screen | Screen Creator |
/fix-shader |
Debug and optimize Metal shaders | Shader Engineer |
/review-architecture |
Review code architecture and patterns | Architecture Advisor |
/validate-screens |
Validate Screen.swift case names and implementations | Screen Validator |
/debug-build |
Diagnose build and CI failures | Build Debugger |
/quality-check |
Run SwiftLint and SwiftFormat checks | Quality Enforcer |
/update-deps |
Update dependencies and tools | Dependency Updater |
/sync-docs |
Synchronize project documentation | Documentation Syncer |
Quick Start
Creating a New Screen
/new-screen
The command will guide you through:
- Naming your screen (e.g., "ParticleExplosion")
- Selecting tags (layout/animation/metal)
- Choosing whether to include Metal shader
- Creating all necessary files
- Validating the build
Fixing Shader Issues
/fix-shader
Use when you encounter:
- Metal compilation errors
- Visual effects not appearing correctly
- Performance issues with GPU rendering
- SwiftUI shader integration problems
Validating Project State
/validate-screens
Runs comprehensive checks:
- JSON structure validation
- Screen ID format verification
- Implementation file existence
- Orphaned file detection
Debugging Build Failures
/debug-build
Diagnoses:
- Swift compilation errors
- Metal shader compilation failures
- SPM plugin issues
- CI/CD pipeline failures
Checking Code Quality
/quality-check
Executes:
- SwiftLint validation
- SwiftFormat checking
- Auto-fixes when possible
- Generates quality report
Reviewing Architecture
/review-architecture
Provides:
- MVVM pattern compliance review
- Swift 6.3 concurrency checks
- YAGNI principle enforcement
- Best practice recommendations
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.
- 6d ago First seen · 320 lines · 0 tokens per session scan A 785381ab544d
README is a command published in the GitHub repository Koshimizu-Takehito/my-toybox (117 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,694 tokens. 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-09-04.
Other commands, from other repositories
tools-pass
Review internal tooling, editor workflows, and automation quality.
patch-notes
Generate patch notes for internal, QA, or player-facing use.
workflow-automate
You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design and implement automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.