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/sumulige/sumulige-claude/fixgit clone --depth 1 https://github.com/sumulige/sumulige-claudeWrote 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/sumulige/sumulige-claude/fix)<a href="https://agentmods.dev/commands/sumulige/sumulige-claude/fix"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/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.00010 | $0.00468 |
| Opus 5 | $0.00005 | $0.00234 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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.
What it actually says
/fix
快速修复构建错误、lint 错误、类型错误。
使用方式
/fix # 自动检测并修复（默认）
/fix --build # 修复构建错误
/fix --lint # 修复 lint 错误
/fix --type # 修复类型错误
/fix --all # 修复所有错误
关联 Skill
此命令加载 quick-fix skill（使用 haiku 模型，快速响应）。
工作流程
Step 1: 错误检测
# 构建错误
npm run build 2>&1 | head -100
# 类型错误
npx tsc --noEmit 2>&1 | head -50
# Lint 错误
npx eslint . --format json 2>&1 | head -100
Step 2: 错误分类
| 类型 | 示例 | 策略 |
|---|---|---|
| 类型错误 | TS2345 |
添加类型或断言 |
| 导入错误 | Cannot find module |
检查路径 |
| 语法错误 | Unexpected token |
修复语法 |
| Lint 错误 | no-unused-vars |
删除或使用 |
Step 3: 增量修复
原则：每次只修复一个错误
1. 读取第一个错误
2. 定位文件和行号
3. 应用最小修复
4. 重新编译验证
5. 重复直到全部修复
Step 4: 输出报告
# Quick Fix Report
## Errors Found: X
## Fixed: Y
## Remaining: Z
| File | Line | Error | Fix |
|------|------|-------|-----|
## Build Status
✅ SUCCESS / ❌ FAILED
原则
- 快速 - 使用轻量模型
- 最小 - 只做必要修改
- 安全 - 不确定的不修复
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 · 84 lines · 10 tokens per session scan A 93ab691be756
fix is a command published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 468 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
doctor
Run read-only health checks on the Kobiton automate plugin (CLI, credentials, profile).
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
handoff
Force a session catchup or a memory promotion outside the hook lifecycle. Default is catchup (read-only); promote is HITL gated.
gate
You are the Gate System controller. Execute quality gate reviews based on the user's request.