Agent skill
audit
Generate usage report for MiniMax and token optimization Use when: (1) /audit is invoked, (2) task relates to audit functionality.
Install this agent skill to your Project
npx add-skill https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/audit
SKILL.md
/audit
Generate usage and cost optimization report.
v2.88 Key Changes (MODEL-AGNOSTIC)
- Model-agnostic: Uses model configured in
~/.claude/settings.jsonor CLI/env vars - No flags required: Works with the configured default model
- Flexible: Works with GLM-5, Claude, Minimax, or any configured model
- Settings-driven: Model selection via
ANTHROPIC_DEFAULT_*_MODELenv vars
What it shows
- Total queries by model (MiniMax M2.1, lightning, Claude)
- Estimated cost savings from MiniMax usage
- Usage trends (daily/weekly)
- Optimization recommendations
Execution
# View stats
mmc --stats
# Detailed audit report
ralph audit
Cost Calculation
- Claude Sonnet: $3.00/$15.00 per 1M tokens (input/output)
- MiniMax M2.1: $0.30/$1.20 per 1M tokens (~92% savings)
- MiniMax-lightning: $0.15/$0.60 per 1M tokens (~96% savings)
Example Output
=== MiniMax Usage Audit ===
Period: Last 7 days
Model Distribution:
MiniMax M2.1: 45 queries (60%)
MiniMax-lightning: 20 queries (27%)
Claude Sonnet: 10 queries (13%)
Estimated Savings:
If all queries used Claude: ~$X.XX
Actual cost with MiniMax: ~$X.XX
Savings: ~XX%
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
browser-test
Browser testing using Chrome DevTools MCP and Playwright for visual verification. Start dev server, navigate, screenshot, Lighthouse audit, console errors, network check. Use when: (1) verifying frontend changes, (2) accessibility auditing, (3) performance testing, (4) visual regression. Triggers: /browser-test, 'test in browser', 'visual test', 'lighthouse audit'.
crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
stop-slop
A skill for removing AI-generated writing patterns ('slop') from prose. Eliminates telltale signs of AI writing like filler phrases, excessive hedging, overly formal language, and mechanical sentence structures. Use when: writing content that should sound human and natural, editing AI-generated drafts, cleaning up prose for publication, or any content that needs to sound authentic rather than AI-generated. Triggers: 'stop-slop', 'remove AI tells', 'clean up prose', 'make it sound human', 'edit AI writing'.
bugs
Bug hunting with Codex CLI Use when: (1) /bugs is invoked, (2) task relates to bugs functionality.
adversarial
Multi-Agent Adversarial Analysis System for code security
senior-software-engineer
Global skill enforcing senior software engineering best practices
Didn't find tool you were looking for?