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-analyze-codescangit 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.00013 | $0.00627 |
| Opus 5 | $0.00006 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
fit-analyze-codescan 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
分析 Code Scanning (CodeQL) 告警 #$1,评估安全风险并创建修复任务。
执行以下步骤:
-
获取告警信息:
gh api repos/{owner}/{repo}/code-scanning/alerts/$1提取: rule (id/severity/description), tool (name/version), most_recent_instance (location/message)
-
创建任务目录和文件:
date +%Y%m%d-%H%M%S mkdir -p .ai-workspace/active/TASK-<timestamp>/使用 Write 工具基于 .agents/templates/task.md 模板创建 task.md:
- codescan_alert_number: $1
- severity, rule_id, tool
- current_step: security-analysis
- assigned_to: codex
-
定位和分析源码:
- 根据 most_recent_instance.location 定位源码文件和行号
- 读取告警所在的源码上下文
- 理解 CodeQL 规则的含义
- 检查是否有其他位置也存在相同问题
-
评估安全风险:
- 代码路径是否可达(外部输入能否到达漏洞点)
- 漏洞的实际影响(是否可被利用)
- 修复的紧急程度和复杂度
-
输出分析文档到 analysis.md,包含:
- 告警基本信息(编号、严重程度、规则 ID、工具)
- 源码位置和代码上下文
- 影响范围评估(受影响代码和相同模式)
- 安全风险评估(可利用性、攻击向量、影响程度)
- 修复建议
- 参考链接
-
更新任务状态:
- current_step: security-analysis
- updated_at: 当前时间
- 标记 analysis.md 为已完成
-
告知用户:
- 输出告警严重程度、任务ID、风险等级
- 提示下一步设计修复方案:
- Claude Code / OpenCode: /plan-task
- Gemini CLI: /fit:plan-task
- Codex CLI: /prompts:fit-plan-task
- 如果是误报，关闭告警:
- Claude Code / OpenCode: /close-codescan $1
- Gemini CLI: /fit:close-codescan $1
- Codex CLI: /prompts:fit-close-codescan $1
注意事项:
- Critical/High 级别立即处理,Medium 计划处理,Low 可延后
- 专注于信息收集和风险评估,不在此阶段制定修复方案
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 · 65 lines · 13 tokens per session scan A f90f6ea05298
fit-analyze-codescan is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 627 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-revise
Revise an existing technical manuscript in Han Hu manuscript mode while preserving scientific evidence, figures, values, citations, and claim boundaries.
me-build-slides
Build a graphics-first thermal-fluid research presentation with slide-to-slide logic, visual plans, speaker notes, and backup-slide structure.
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.