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/create-prgit 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.00006 | $0.00859 |
| Opus 5 | $0.00003 | $0.00430 |
| Sonnet 5 | $0.00001 | $0.00172 |
| Haiku 4.5 | $0.00001 | $0.00086 |
Grade A, and why
create-pr 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
Create PR Command
功能说明
创建 Pull Request 到指定分支(默认: 当前分支)。
用法
/create-pr- 创建PR到当前分支/create-pr main- 创建PR到 main 分支/create-pr <branch-name>- 创建PR到指定分支
执行步骤
1. 确定目标分支
- 如果用户提供了参数(如
main,3.5.x,develop等),使用该参数作为目标分支 - 如果没有参数,自动推断目标分支:
推断规则:git branch --show-current git log --oneline --decorate --first-parent -20- 当前在核心分支上(main 或版本号分支如 大版本号.小版本号.x(如 3.6.x))→ 目标分支即为当前分支
- 当前在特性分支上 → 从 log 中的分支标记找到最近的父核心分支作为目标
- 无法确定时 → 询问用户
2. 读取 PR 模板
必须执行:
Read(".github/PULL_REQUEST_TEMPLATE.md")
3. 查看最近 3 个 merged PR 作为参考
必须执行:
gh pr list --limit 3 --state merged --json number,title,body
4. 分析当前分支的完整变更
- 运行
git status查看当前状态 - 运行
git log <target-branch>..HEAD --oneline查看所有提交 - 运行
git diff <target-branch>...HEAD --stat查看变更统计 - 运行
git diff <target-branch>...HEAD查看详细变更(如果需要)
5. 检查远程分支状态
git rev-parse --abbrev-ref --symbolic-full-name @{u}
6. 如果分支未推送,先推送
git push -u origin <current-branch>
7. 根据模板创建 PR
- 按照
.github/PULL_REQUEST_TEMPLATE.md格式填写所有部分 - 参考最近的 PR 格式和风格
- 使用 HEREDOC 格式传递 body
- PR 结尾必须添加:
🤖 Generated with [Claude Code](https://claude.com/claude-code)
gh pr create --base <target-branch> --title "<标题>" --body "$(cat <<'EOF'
<完整的PR描述>
EOF
)"
8. 提示下一步
PR 创建成功后,输出 PR 链接,并提示下一步:
✅ PR 已创建: {pr-url}
**下一步**:
如果在任务工作流中,同步进度到 PR:
- Claude Code / OpenCode: `/sync-pr {task-id}`
- Gemini CLI: `/fit:sync-pr {task-id}`
- Codex CLI: `/prompts:fit-sync-pr {task-id}`
或标记任务完成:
- Claude Code / OpenCode: `/complete-task {task-id}`
- Gemini CLI: `/fit:complete-task {task-id}`
- Codex CLI: `/prompts:fit-complete-task {task-id}`
注意事项
- 必须严格遵循 PR 模板格式
- 所有必填项都要填写完整
- 参考最近的 merged PR 的格式和风格
- 确保 PR 标题格式正确(如:
[模块名] 简短描述)
相关命令
/sync-pr <task-id>- 同步进度到 PR/commit- 提交代码/review-task- 代码审查
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 · 111 lines · 6 tokens per session scan A 993d85570f6b
create-pr is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 859 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
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.