FIT is an enterprise AI development framework with a multilingual function engine, a flow orchestration engine, and Java tools for connecting language models, knowledge bases, and external tools. It is for Java-oriented teams building AI applications that can run locally or in distributed deployments with plugins. The catalogue add-ons provide commands, skills, instructions, and settings for working with FIT.
Borrowing it
Nothing to install: this file belongs to ModelEngine-Group/fit-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ModelEngine-Group/fit-framework/main/.codex/commands/fit-plan-task.mdgit clone --depth 1 https://github.com/ModelEngine-Group/fit-frameworkWrote 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/commands/modelengine-group/fit-framework/fit-plan-task)<a href="https://agentmods.dev/commands/modelengine-group/fit-framework/fit-plan-task"><img src="https://agentmods.dev/badge/commands/modelengine-group/fit-framework/fit-plan-task.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.00009 | $0.00607 |
| Opus 5 | $0.00005 | $0.00303 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
fit-plan-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 3d 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 如果都不存在,提示用户任务不存在。
-
读取需求分析: 读取 analysis.md,理解:
- 问题的根本原因和影响范围
- 技术约束和特殊要求
- 相关文件和依赖关系
-
设计解决方案:
- 提出多个可行方案并对比优劣(效果、成本、风险、可维护性)
- 选择最合适的方案并说明理由
- 制定详细的实施步骤
- 列出需要创建/修改的文件清单
- 设计验证策略(测试、验证、回归检查)
- 评估影响(性能、安全、兼容性)
- 制定风险控制和回滚方案
-
输出方案文档: 创建 .ai-workspace/active/$1/plan.md(或对应状态目录),包含:
- 方案决策(问题理解、约束条件、备选方案对比、最终选择)
- 技术方案(核心策略、关键技术点、具体实现细节)
- 实施步骤(每步的操作和预期结果)
- 文件清单(需要创建和修改的文件)
- 验证策略(功能验证、问题验证、回归验证)
- 影响评估(性能、安全、兼容性)
- 风险控制(潜在风险和回滚方案)
-
更新任务状态: 使用 Edit 工具更新 task.md:
- current_step: technical-design
- assigned_to: codex
- updated_at: 当前时间
- 标记 plan.md 为已完成
- 在"工作流进度"中标记 technical-design 为完成 ✅
-
告知用户:
- 输出方案名称、工作量、风险等级
- ⚠️ 提示这是人工审查检查点,请审查技术方案是否合理
- 审查通过后开始实施:
- Claude Code / OpenCode: /implement-task $1
- Gemini CLI: /fit:implement-task $1
- Codex CLI: /prompts:fit-implement-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.
- 3d ago First seen · 61 lines · 9 tokens per session scan A 6fac9f5e05da
fit-plan-task is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,115 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 607 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-09-03.
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.
status
Display project status, active tracks, and next actions.
discuss
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).