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-block-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.00010 | $0.00733 |
| Opus 5 | $0.00005 | $0.00367 |
| Sonnet 5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
fit-block-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.
What it actually says
标记任务 $1 为阻塞状态,记录详细的阻塞原因,并移动到 blocked 目录。
使用场景:
- ❌ 编译失败且无法修复
- ❌ 测试失败且原因不明
- ❌ 依赖库存在 Bug
- ❓ 需求不明确,需要澄清
- ⏳ 等待外部依赖
不应该标记为阻塞:
- ✅ 代码审查发现问题 → 使用 /refine-task $1 修复
- ✅ 实现遇到困难但可以解决 → 继续实施
执行以下步骤:
-
验证任务存在:
test -f .ai-workspace/active/$1/task.md && echo "✅ 任务存在" || echo "❌ ERROR: 任务不存在" -
分析并记录阻塞原因: 用户提供的阻塞原因: $2 如果上述值为空,需要询问用户确定阻塞原因。 确定以下信息:
- 阻塞类型: 技术问题/需求问题/资源问题/决策问题
- 问题描述、根本原因、尝试的解决方案、需要的帮助
-
获取当前时间:
date '+%Y-%m-%d %H:%M:%S' -
更新任务状态: 使用 Edit 工具更新 task.md:
- status: blocked
- updated_at: 当前时间
- blocked_at: 当前时间
- blocked_by: codex
- blocked_reason: 简短描述阻塞原因
-
在 task.md 中添加"⚠️ 阻塞信息"章节(阻塞概要、问题描述、根本原因、尝试方案、解除条件)
-
移动到阻塞目录:
mkdir -p .ai-workspace/blocked && mv .ai-workspace/active/$1 .ai-workspace/blocked/ -
验证移动成功:
test ! -d .ai-workspace/active/$1 && echo "✅ 已移除 active" || echo "❌ active 仍存在" test -d .ai-workspace/blocked/$1 && echo "✅ 已移动到 blocked" || echo "❌ 移动失败" -
告知用户:
⚠️ 任务 $1 已标记为阻塞 阻塞位置: .ai-workspace/blocked/$1/- 提示下一步:
- 解决阻塞问题后手动移回 active 目录
- 恢复后查看任务状态:
- Claude Code / OpenCode: /check-task $1
- Gemini CLI: /fit:check-task $1
- Codex CLI: /prompts:fit-check-task $1
- 提示下一步:
解除阻塞:
mv .ai-workspace/blocked/$1 .ai-workspace/active/
然后更新 task.md: status 改回 active,移除 blocked 相关字段。
注意事项:
- 阻塞信息要详细、准确、客观
- 标记后要主动跟进问题解决进度
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 · 80 lines · 10 tokens per session scan A f3b5c76511c5
fit-block-task is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 733 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
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.
me-lit-matrix
Build a thermal-fluid literature matrix organized by mechanism, method, metric, validity range, benchmark value, and unresolved gap.