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/fit-check-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.00008 | $0.00627 |
| Opus 5 | $0.00004 | $0.00313 |
| Sonnet 5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
fit-check-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 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.
What it actually says
查看任务 $1 的当前状态、进度和上下文文件。
执行以下步骤:
-
查找任务文件: 按以下优先级搜索:
- .ai-workspace/active/$1/task.md(优先)
- .ai-workspace/blocked/$1/task.md
- .ai-workspace/completed/$1/task.md 如果都不存在,提示用户任务不存在。
-
读取任务信息: 从 task.md 中获取: id, type, workflow, status, current_step, assigned_to, created_at, updated_at
-
检查上下文文件是否存在:
- analysis.md - 需求分析
- plan.md - 技术方案
- implementation.md - 实现报告
- review.md - 审查报告
-
输出状态报告:
📋 任务状态报告 **基本信息**: - 任务ID: $1 - 任务标题: <title> - 任务类型: <type> - 创建时间: <created_at> **当前状态**: - 工作流: <workflow> - 当前步骤: <current_step> - 执行者: <assigned_to> **工作流进度**: ✅ / ⏳ / ⏸️ 各步骤状态 **上下文文件**: ✅ / ❌ 各文件存在状态 **下一步建议**: 根据当前状态给出具体命令建议
下一步建议规则:
- 需求分析完成:
- Claude Code / OpenCode: /plan-task $1
- Gemini CLI: /fit:plan-task $1
- Codex CLI: /prompts:fit-plan-task $1
- 技术方案完成 → ⚠️ 等待人工审查,审查通过后:
- Claude Code / OpenCode: /implement-task $1
- Gemini CLI: /fit:implement-task $1
- Codex CLI: /prompts:fit-implement-task $1
- 实现完成:
- Claude Code / OpenCode: /review-task $1
- Gemini CLI: /fit:review-task $1
- Codex CLI: /prompts:fit-review-task $1
- 审查完成(批准):
- Claude Code / OpenCode: /commit
- Gemini CLI: /fit:commit
- Codex CLI: /prompts:fit-commit
- 审查完成(需修改):
- Claude Code / OpenCode: /refine-task $1
- Gemini CLI: /fit:refine-task $1
- Codex CLI: /prompts:fit-refine-task $1
- 任务阻塞 → 显示阻塞原因和解除条件
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 · 73 lines · 8 tokens per session scan A 4ef7fd6c6f49
fit-check-task is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 627 once invoked, about $0.0000 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
backlog-status
Display a live backlog status dashboard — active tasks table with PR state and branch-to-test. Optional flag: --qa also generates a QA test guide for all Ready-for-Review tasks.
backlog-list
Skills: agent-flow-init-check.
plan
Guide a collaborative planning session. Conducts Socratic dialogue, spawns explorer on large repos and researcher on new deps; saves plan + backlog task.
team
The team command manages team members and messages for your Codev project. Team data is stored in codev/team/ and displayed in the Tower dashboard.
cycle-design
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/ and sources the cycle from them when relevant.
cycle-start
Activate a cycle and start implementing its stories.