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.
npx agentmods add commands/kaelsensei/magicaibuilder/fixgit clone --depth 1 https://github.com/KaelSensei/MagicAIBuilderWrote 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/kaelsensei/magicaibuilder/fix)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/fix"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/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 | $0.00000 | $0.00913 |
| Opus 5 | $0.00000 | $0.00456 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00091 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Command – Issue Resolution Workflow
When /fix <issue description> is invoked, immediately execute the following steps.
Step 1: Load Project Context
- Assume the project root as the working directory
- Load and respect all Cursor rules from
.cursor/rules/*.mdc - Read core project documentation if present:
README.mdPROGRESS.md- Architecture or task documents relevant to the issue
- Identify the current Git branch and assume it is a fix branch, not
main - Check for attachments (screenshots, error logs, stack traces, videos):
- Analyze any visual evidence of the issue
- Extract error messages, console output, or visual bugs from images
- Review stack traces or debug information if provided
- Use attachments to understand the exact failure scenario
- If attachments show different issues than described, ask for clarification
Step 2: Understand the Issue
- Parse the issue description provided after
/fix - Incorporate context from any attached evidence:
- Screenshots showing UI bugs or unexpected behavior
- Error messages or console logs
- Stack traces pointing to problematic code
- Before/after comparisons
- Network request failures or API errors
- Determine:
- Is this a bug, security issue, regression, or logic flaw
- Which layer is affected (React Native UI, SQLite, scraping, image caching, TypeScript)
- Locate the exact code paths involved
- Cross-reference visual evidence with code to pinpoint root cause
- Do not assume the fix — verify by reading the code first
Step 3: Security & Safety Check (Mandatory)
Before writing any code:
- Treat the issue as potentially security-sensitive
- Check for:
- Backdoors or hidden logic
- Unsafe external calls (only Moxfield/Scryfall should be called)
- SQL injection risks
- File system access issues
- Dependency or supply-chain risks
- If attachments show suspicious behavior (unexpected network calls, unauthorized data access):
- Investigate thoroughly before proceeding
- Flag potential security implications
- Use MCP (Model Context Protocol) or equivalent security reasoning to:
- Validate the fix does not introduce new vulnerabilities
- Ensure no malicious patterns are added
- If security implications are unclear, stop and ask before proceeding
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 · 125 lines · 0 tokens per session scan A f2095c952259
fix is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 913 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-08-31.
Other commands, from other repositories
spec-plan
Step 4 of the Vibe-Spec workflow. Generate the high-level plan file for every phase in the V2 phase index, each with a scope + status header, so the user has a complete set of plan files to work from.
spec-phases
Step 3 of the Vibe-Spec workflow. Break the V1 spec into sequential, self-contained phases and append a phase index, producing the final V2 spec.
spec-secrets
Audit a Vibe-Spec app for secrets leaking to the browser. A locked-down, redacting command — a local script reads .env and the built bundle, and Claude only ever sees variable NAMES and pass/fail verdicts. Secret values never enter the model's context.
spec-setup
Guided environment setup for the Vibe-Spec stack. Figures out which tools your project needs (from your spec, or by project type), checks what's missing, and helps you install only the gaps — proposing exact per-OS commands and running each only after you confirm.
spec-doctor
Read-only environment health check for the Vibe-Spec stack. Detects your OS and reports which prerequisite tools (Git, Node, pnpm, Docker, uv) are installed, their versions, and what each is needed for. Installs nothing.
spec-implement
Step 5 of the Vibe-Spec workflow. Promote a phase plan to detailed, implement it following the vibe-spec references, then update the docs so the spec reflects reality.