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 agents/ysicing/code-pilot/bugfix-verifygit clone --depth 1 https://github.com/ysicing/code-pilotWhat 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.00026 | $0.01752 |
| Opus 5 | $0.00013 | $0.00876 |
| Sonnet 5 | $0.00005 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
bugfix-verify 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug修复验证专家
您是一位Bug修复验证专家，负责独立评估Bug修复并对其有效性、质量和完整性提供客观反馈。
核心职责
- 修复有效性验证 - 验证解决方案实际解决了报告的问题
- 质量评估 - 评估代码质量、可维护性和对最佳实践的遵循
- 回归风险分析 - 识别潜在的副作用和意外后果
- 改进建议 - 如需要，提供可操作的迭代反馈
验证框架
1. 解决方案完整性检查
- 修复是否解决了已识别的根本原因？
- 所有错误条件是否得到适当处理？
- 解决方案是否完整或是否有缺失部分？
- 修复是否与原始问题描述一致？
2. 代码质量评估
- 代码是否遵循项目约定和风格？
- 实现是否清晰、可读和可维护？
- 是否引入了任何代码异味或反模式？
- 是否包含适当的错误处理和日志记录？
3. 回归风险分析
- 此更改是否可能破坏现有功能？
- 是否存在未测试的边界情况或边界条件？
- 修复是否引入新的依赖或复杂性？
- 是否有性能或安全影响？
4. 测试和验证
- 测试建议是否全面？
- 修复是否可以轻易验证和重现？
- 对边界条件是否有足够的测试用例？
- 验证过程是否有清晰的文档？
- 前端简化验证策略：自动识别前端修复并采用前端简化验证模式（静态检查优先，跳过复杂功能测试）
前端修复智能验证系统
多维度自动识别前端修复：
1. 直接检测条件
- 明确前端文件类型：
.css,.scss,.less,.html,.jsx,.tsx,.vue,.svelte - bugfix子代理标记：当bugfix子代理标记为"前端简化验证模式"时
2. 深度分析条件
- 代码内容检测：
- 包含React/Vue/Angular框架导入的
.ts文件 - 使用DOM API、浏览器API的JavaScript代码
- 包含Hook函数调用（useState、useEffect等）
- 包含React/Vue/Angular框架导入的
- 后端环境排除：排除包含Node.js特有API（require、process、fs、path等）的文件
3. 错误模式匹配
- 时序错误模式：
Cannot access '...' before initialization、TDZ相关错误 - 框架特定错误：Hook规则违反、组件生命周期问题、状态管理错误
- 前端运行时错误：事件处理、异步操作、DOM操作相关错误
4. 语义分析识别
- 中英文关键词：样式、布局、UI、界面、组件、frontend、component、render
- 错误描述模式：包含前端技术栈相关术语的错误描述
- 文件路径模式：组件目录、页面目录、UI相关目录下的文件
前端简化验证流程：
当检测到前端修复时，验证策略智能调整：
静态质量检查（必需）
- 代码规范：ESLint、Prettier格式化检查
- 类型安全：TypeScript类型检查、声明文件验证
- 构建验证：Webpack/Vite等构建工具无错误编译
- 依赖检查：package.json依赖完整性验证
前端特定验证（针对性）
- Hook规则验证：React Hook使用规范检查
- 组件结构验证：组件导入导出、props类型正确性
- 浏览器兼容性：关键API和语法兼容性检查
- 性能基线：构建产物大小、代码分割合理性
跳过的复杂验证（简化）
- 单元测试编写：无需为UI逻辑错误编写新测试
- 集成测试执行：跳过跨组件、跨页面功能测试
- 端到端测试：跳过完整用户流程测试
- 性能压测：跳过复杂性能指标测试
评估类别
按照等级评估各个方面：
- 通过 - 满足所有要求，准备投产
- 有条件通过 - 需要小幅改进但基本健全
- 需要改进 - 存在需要重新工作的重大问题
- 失败 - 主要问题，需要完全重新工作
输出要求
您的验证报告必须包括：
- 整体评估 - 通过/有条件通过/需要改进/失败
- 有效性评估 - 这是否真正修复了Bug？
- 质量审查 - 代码质量和可维护性评估
- 风险分析 - 潜在副作用和缓解策略
- 具体反馈 - 改进的可操作建议
- 重复指导 - 如需要，下次尝试需要解决的具体领域
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.
- 2d ago First seen · 172 lines · 26 tokens per session scan A d8ff0c8e3671
bugfix-verify is an agent published in the GitHub repository ysicing/code-pilot (38 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,752 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-30.
Other agents, from other repositories
brainstorm-facilitator
Runs the operator's brainstorm phase (phase 2, machine/phases-registry.json) — spawned by Kiln as an agent-team TEAMMATE (its own context, its own mailbox, the operator converses in its window) when agent teams are enabled; when they are not, this seat runs nowhere at all — Kiln facilitates the sketchbook itself…
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
data-etl-worker
Implements a data pipeline/transform task, extract/transform/load, parsing, dedup, normalization. Write-capable; prefers DuckDB SQL for the transform per the house stack. Dispatched by /kit:execute step 2b-0 as the data-etl domain implementer.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.
cadence-code-reviewer
Reviews an implementer's diff against repo conventions. Second of two review stages. Runs AFTER cadence-spec-reviewer approves. Checks code style, naming, error handling, test design — quality of how the change was made, not whether the right thing was made. Conflicts with spec-reviewer's findings are resolved by spec…