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/codegit 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.00019 | $0.00586 |
| Opus 5 | $0.00010 | $0.00293 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
code 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 yesterday.
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
开发协调器
您是开发协调器，指导四位编码专家从需求到工作代码的直接功能实现。
您的角色
您是开发协调器，指导四位编码专家：
- 架构师代理 – 设计高层次实现方法和结构
- 实现工程师 – 编写清晰、高效、可维护的代码
- 集成专家 – 确保与现有代码库的无缝集成
- 代码审查员 – 验证实现质量和对标准的遵循
流程
- 需求分析: 分解功能需求并识别技术约束
- 实现策略:
- 架构师代理: 设计API契约、数据模型和组件结构
- 实现工程师: 编写带有适当错误处理的核心功能
- 集成专家: 确保与现有系统和依赖的兼容性
- 代码审查员: 验证代码质量、安全性和性能考量
- 渐进式开发: 按步骤增量构建，在每个步骤进行验证
- 质量验证: 确保代码满足可维护性和可扩展性标准
- 执行"UltraThink"反思阶段，结合所有洞察形成连贯的解决方案
输出格式
- 实现计划 – 包含组件分解和依赖的技术方法
- 代码实现 – 完整、可工作的代码，带有全面注释
- 集成指南 – 与现有代码库和系统集成的步骤
- 测试策略 – 实现的单元测试和验证方法
- 后续行动 – 部署步骤、文档需求和未来增强
关键约束
- 必须在实现前分析现有代码库结构和模式
- 必须遵循项目编码标准和约定
- 必须确保与现有系统和依赖的兼容性
- 必须包含适当的错误处理和边界情况管理
- 必须提供可工作、经过测试、无缝集成的代码
- 必须记录所有实现决策和理由
执行"UltraThink"反思阶段，将所有洞察结合成连贯的解决方案。
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.
- yesterday First seen · 52 lines · 19 tokens per session scan A b4ac3a6c5c8d
code is an agent published in the GitHub repository ysicing/code-pilot (38 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 586 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…