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 skills/sumulige/sumulige-claude/quick-fixnpx skills add sumulige/sumulige-claude --skill quick-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/skills/sumulige/sumulige-claude/quick-fix)<a href="https://agentmods.dev/skills/sumulige/sumulige-claude/quick-fix"><img src="https://agentmods.dev/badge/skills/sumulige/sumulige-claude/quick-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.00820 |
| Opus 5 | $0.00000 | $0.00410 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
quick-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 5d 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
Quick Fix
快速修复者 - 优化版 build-error-resolver
核心职责
快速修复常见的开发问题：
- 构建错误 - TypeScript 编译错误
- Lint 错误 - ESLint/Prettier 问题
- 类型错误 - 类型不匹配、缺少类型
设计理念
轻量 + 快速 + 最小变更
使用 haiku 模型，确保响应快速，成本低。
工作流程
1. 错误捕获
# 获取构建错误
npm run build 2>&1 | head -100
# 获取类型错误
npx tsc --noEmit 2>&1 | head -50
# 获取 lint 错误
npx eslint . --format json 2>&1 | head -100
2. 错误分类
| 类型 | 示例 | 处理策略 |
|---|---|---|
| 类型错误 | TS2345: Argument of type... |
添加类型断言或修复类型 |
| 导入错误 | Cannot find module... |
检查路径或安装依赖 |
| 语法错误 | Unexpected token... |
修复语法 |
| Lint 错误 | no-unused-vars |
删除或使用变量 |
3. 增量修复
原则：每次只修复一个错误
流程：
1. 读取第一个错误
2. 定位问题文件和行号
3. 应用最小修复
4. 重新编译验证
5. 如果仍有错误，重复步骤 1
常见修复模式
类型错误
// 错误: Type 'string | undefined' is not assignable to type 'string'
// 修复 1: 非空断言
const value = maybeString!
// 修复 2: 默认值
const value = maybeString ?? ''
// 修复 3: 类型守卫
if (maybeString) {
const value = maybeString
}
导入错误
// 错误: Cannot find module './utils'
// 检查 1: 文件是否存在
// 检查 2: 路径是否正确
// 检查 3: 扩展名是否需要
// 修复: 更正路径
import { helper } from './utils/helpers'
Lint 错误
// 错误: 'foo' is defined but never used
// 修复 1: 删除未使用的变量
// 修复 2: 如果需要保留，使用 _ 前缀
const _foo = unused
输出格式
# Quick Fix Report
## Errors Found: X
## Fixed: Y
## Remaining: Z
## Fixes Applied
| File | Line | Error | Fix |
|------|------|-------|-----|
| src/app.ts | 42 | TS2345 | Added type assertion |
| src/utils.ts | 15 | no-unused-vars | Removed unused import |
## Build Status
✅ SUCCESS / ❌ FAILED (X errors remaining)
使用方式
# 修复构建错误
/fix --build
# 修复 lint 错误
/fix --lint
# 修复类型错误
/fix --type
# 自动修复所有
/fix --all
限制
- 不处理复杂的架构问题
- 不重构代码
- 仅做最小必要的修改
- 如果错误过于复杂，建议使用
/plan先规划
原则：快速、最小、安全。不确定的修复不要做。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 139 lines · 0 tokens per session scan A c0c234f582b7
quick-fix is a skill published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 820 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 skills, from other repositories
codex-build
Orchestrate Codex to BUILD code in the background while this Claude Code session (typically Opus) plans and reviews — never babysitting. The session composes the implementation plan, kicks the dev-review runner detached via a background Bash task with --preset codex-build, ENDS ITS TURN, and is woken on exit to run a…
co-evolution
General-purpose co-evolution for questions, ideas, drafts, plans, specs, arguments, and markdown documents. Composes or bounces content between agents using [CONTESTED]/[CLARIFY] markers until it converges. Triggers on "co-evolution", "co-evolve", "co evolve", "bounce", "bounce document", "agent bouncer", "refine with…
recursive-task-optimizer
Build, configure, run, inspect, or troubleshoot agent-agnostic recursive improvement loops for a repository or artifact. Use when a task should be attempted repeatedly by Claude Code, Codex CLI, Hermes, or another CLI agent; when candidates must inherit mutable task instructions, a self-improving meta-procedure, and…
dev-review
Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the…
cao-workflow
Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…
aidlc-portfolio
Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…