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-close-dependabotgit 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-close-dependabot)<a href="https://agentmods.dev/commands/modelengine-group/fit-framework/fit-close-dependabot"><img src="https://agentmods.dev/badge/commands/modelengine-group/fit-framework/fit-close-dependabot.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 | $0.00013 | $0.00528 |
| Opus 5 | $0.00006 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
fit-close-dependabot 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 4d 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
关闭 Dependabot 安全告警 #$1。在关闭前会要求用户确认并提供合理的理由。
执行以下步骤:
-
获取安全告警信息:
gh api "repos/{owner}/{repo}/dependabot/alerts/$1"验证告警状态: 如果已是 dismissed 或 fixed,提示用户并退出。
-
展示告警详情:
🔒 安全告警 #$1 严重程度: <severity> 漏洞: <summary> 受影响包: <package-name> 修复版本: <first-patched-version> -
询问关闭理由: 选项:
- 误报(False Positive) - 漏洞代码路径未被使用
- 无法利用(Not Exploitable) - 当前场景下无法被利用
- 已有缓解措施(Mitigated)
- 无修复版本且风险可接受
- 测试或开发依赖(Dev Only)
- 取消 - 不关闭
-
要求详细说明(最少 20 个字符)
-
最终确认后执行关闭:
gh api --method PATCH "repos/{owner}/{repo}/dependabot/alerts/$1" -f state=dismissed -f dismissed_reason="<reason>" -f dismissed_comment="<comment>" -
告知用户:
✅ 安全告警 #$1 已关闭 关闭理由: <理由> 查看链接: https://github.com/<owner>/<repo>/security/dependabot/$1- 提示下一步:
- 如果还有其他待处理的安全告警:
- Claude Code / OpenCode: /analyze-dependabot {alert-number}
- Gemini CLI: /fit:analyze-dependabot {alert-number}
- Codex CLI: /prompts:fit-analyze-dependabot {alert-number}
- 如果还有其他待处理的安全告警:
- 提示下一步:
注意事项:
- 谨慎关闭高危告警(Critical/High)
- 关闭应该是最后选择,优先考虑修复
- 建议先使用 /analyze-dependabot $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.
- 4d ago First seen · 58 lines · 13 tokens per session scan A 2bdcb81adb04
fit-close-dependabot is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,116 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 528 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
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).