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/modelengine-group/fit-framework/complete-taskgit clone --depth 1 https://github.com/ModelEngine-Group/fit-frameworkWhat 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.00014 | $0.02304 |
| Opus 5 | $0.00007 | $0.01152 |
| Sonnet 5 | $0.00003 | $0.00461 |
| Haiku 4.5 | $0.00001 | $0.00230 |
Grade A, and why
complete-task 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Task Command
功能说明
标记任务为已完成状态,更新任务元数据,并将任务从 active 目录移动到 completed 目录进行归档。
⚠️ CRITICAL: 状态更新要求
执行此命令后,你必须立即更新任务状态并移动任务目录。参见规则 7。
前置条件
在执行此命令前,请确认以下条件全部满足:
- 所有工作流步骤已完成
- 代码已审查通过(review.md 显示批准)
- 代码已提交到 Git
- 代码已合并到目标分支(如果需要)
- 所有测试通过
- Issue 已同步更新(如果有关联 Issue)
- PR 已合并(如果有 PR)
如果以上条件未全部满足,请勿执行此命令。
执行流程
1. 验证任务存在
检查任务文件是否存在:
ls -la .ai-workspace/active/{task-id}/task.md
如果任务不在 active 目录,检查是否已经在 completed 或 blocked 目录。
2. 读取并验证任务状态
读取 .ai-workspace/active/{task-id}/task.md,检查:
工作流进度:
- 所有步骤是否标记为完成 ✅
current_step是否为最后一步(如finalize或code-review)
任务状态:
status是否为active(即将改为completed)- 是否有未解决的阻塞问题
文件完整性:
-
analysis.md存在(如果是 feature-development 或 security-fix) -
plan.md存在(如果是 feature-development) -
implementation.md存在 -
review.md存在且显示批准
如果发现任何问题,提示用户并停止执行。
3. 更新任务状态 (CRITICAL)
必须更新 .ai-workspace/active/{task-id}/task.md:
status: completed
current_step: finalize
updated_at: {当前时间,格式: yyyy-MM-dd HH:mm:ss}
completed_at: {当前时间,格式: yyyy-MM-dd HH:mm:ss}
在工作流进度中标记所有步骤完成:
## 工作流进度
- [x] requirement-analysis (claude, {日期})
- [x] technical-design (claude, {日期})
- [x] implementation (claude, {日期})
- [x] code-review (claude, {日期})
- [x] finalize (claude, {当前日期}) ← 标记为完成
添加完成总结(在 task.md 末尾添加):
---
## 任务完成总结
### 完成信息
- **完成时间**: {当前时间}
- **完成者**: {当前AI}
- **关联 PR**: #{pr-number}(如果有)
- **关联 Issue**: #{issue-number}(如果有)
- **目标分支**: {分支名}
### 交付成果
- [x] 需求分析文档: `analysis.md`
- [x] 技术方案文档: `plan.md`
- [x] 实现报告: `implementation.md`
- [x] 代码审查报告: `review.md`
- [x] 代码提交: {commit-hash}
- [x] PR 合并: #{pr-number}
### 任务完成标准
- [x] 功能完整实现
- [x] 代码审查通过
- [x] 所有测试通过
- [x] 文档完整
- [x] 代码已合并
### 备注
{如有需要,添加备注}
4. 归档任务 (CRITICAL)
将任务从 active 目录移动到 completed 目录:
# 确保 completed 目录存在
mkdir -p .ai-workspace/completed
# 移动任务目录
mv .ai-workspace/active/{task-id} .ai-workspace/completed/
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 · 304 lines · 14 tokens per session scan A 02c7ee83ea55
complete-task is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 2,304 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 commands, from other repositories
overview
Codev provides three CLI tools for AI-assisted software development.
me-han-hu-draft
Draft a technical manuscript section in Han Hu manuscript mode using the private calibrated style corpus and evidence-preserving engineering workflow.
me-cfd-review
Review thermal-fluid CFD setup, boundary conditions, mesh, wall treatment, convergence, validation, and whether the claims are supported.
me-code-sanity
Run a fast preflight on thermal-fluid research code for units, baselines, leakage, physics checks, and result traceability.
me-correlation-check
Check thermal-fluid equations, empirical correlations, and dimensionless groups for validity range, assumptions, units, and claim strength.
me-experiment-plan
Plan thermal-fluid experiments with instrumentation, calibration, uncertainty, repeatability, heat-loss correction, operating envelope, and safety checks.