Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-cli. 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/namastexlabs/automagik-cli/main/.claude/commands/fix.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/fix)<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/fix"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/fix.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.00000 | $0.02148 |
| Opus 5 | $0.00000 | $0.01074 |
| Sonnet 5 | $0.00000 | $0.00430 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade A, and why
fix 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 3d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fix
allowed-tools: mcp__zen__debug(), Task(), Read(), Edit(), MultiEdit(), Write(), Bash(), Glob(), Grep(), mcp__gemini__, mcp__search-repo-docs__, mcp__ask-repo-agent__, mcp__genie_memory__, mcp__send_whatsapp_message__, mcp__wait__* description: Unified debugging and fixing command with multiple investigation strategies
Comprehensive debugging and fixing command that unifies systematic debugging with intelligent strategy selection for different problem complexities.
Auto-Loaded Project Context:
@/CLAUDE.md @/docs/ai-context/project-structure.md @/docs/ai-context/docs-overview.md
Debugging Strategies
Simple Strategy (default)
# Quick debugging for obvious issues (replaces /debug default)
/fix "API returns 500 error when uploading files"
/fix "Payment processing failing for new users" model="o3"
Systematic Strategy
# Multi-step investigation (original /fix behavior)
/fix "Memory leak in agent sessions" strategy="systematic"
/fix "Database connection timeouts under load" strategy="systematic"
Multi-Agent Strategy
# Parallel debugging teams (from original /fix multi-agent)
/fix "Race condition in agent routing system" strategy="multi-agent"
/fix "Complex integration failure" strategy="multi-agent"
Expert Strategy
# With expert consultation (enhanced debugging)
/fix "Mysterious performance degradation" strategy="expert"
/fix "Complex architectural issue" strategy="expert" model="gemini"
Usage Examples
# Default (uses Claude with simple strategy)
/fix "API returns 500 error"
# With specific model and strategy
/fix "Race condition in payment processing" strategy="multi-agent" model="o3"
/fix "Memory leak in agent sessions" strategy="systematic" model="grok"
Model Strengths
- Claude (default): Full project context, holistic debugging
- O3: Systematic reasoning, logical deduction, step-by-step analysis
- Grok: Large context for complex traces, performance issues
- Gemini: Creative problem-solving, architectural insights
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.
- 3d ago First seen · 286 lines · 0 tokens per session scan A 976cecf48df8
fix is a command published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,148 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.