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/nongjun/awesome-harness-engineering/gitgit clone --depth 1 https://github.com/nongjun/awesome-harness-engineeringWhat 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.00000 | $0.00864 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
Git提交和推送 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
Git 提交和推送命令
当用户调用此命令时，执行以下操作：
目标仓库
- 默认仓库：当前工作区根目录
- 自动检测已配置的远程仓库（origin 及其他远程）
- 所有 git 操作通过本命令执行
操作步骤
设计原则：先提交再拉取，本地更改始终安全保存在提交中
0. 健康检查（自动执行，有问题才输出）
检查并自动修复常见的 Git 仓库问题：
- 如果存在 stash，清理掉（本项目禁止使用 stash）
- 如果 index 文件损坏（存在未解决的合并冲突标记），重建 index
1. 检查 Git 状态
- 运行
git status查看当前工作区 - 如果没有任何更改，提示用户并结束
2. 提交代码
git add -A- 分析改动内容，生成提交信息：
- 格式：
[类型] 简要描述 - 类型：feat / fix / docs / style / refactor / chore
- 多模块改动时：第一行概括，下方按模块列出要点
- 格式：
git commit -m "提交信息"
3. 拉取远程更新
git pull --rebase origin <当前分支>- rebase 保持线性历史，不同文件会自动合并
4. 推送到远程
- 自动检测所有已配置的远程仓库，并行推送
- 对非主远程设置 45 秒超时（网络不稳定时），超时不阻塞，提示后续手动重试即可
- 新分支使用
git push -u
5. Subtree 子仓库同步
如果项目使用 git subtree，自动检测并同步：
- 通过
.gitsubtree配置或git log --grep="git-subtree-dir"自动发现 subtree 映射关系 - 推送：子仓库不能用普通
git push，必须用git subtree push --prefix=<路径> <远程名> <分支> - 拉取：从子仓库远程拉取更新用
git subtree pull --prefix=<路径> <远程名> <分支> --squash - 在步骤 4 推送主仓库远程时，自动识别 subtree 远程并跳过普通推送，改用 subtree push
- subtree 操作需要遍历提交历史，耗时较长属正常现象
6. 输出结果表格
| 步骤 | 状态 |
|------|------|
| 健康检查 | ✅ / ⚠️ 已修复 |
| 提交 | ✅ commit_hash — 文件数, +增/-删 |
| 拉取更新 | ✅ / 合并了 N 个提交 |
| 推送 origin | ✅ / ❌ |
| 推送 其他远程 | ✅ / ⏳ 超时 |
| 子仓库 subtree | ✅ / ❌ / 无 subtree |
示例提交信息
单模块：
[feat] 添加用户登录功能
多模块：
[feat] 用户管理优化与消息模块增强
用户管理:
- 新增批量导入功能
- 权限校验优化
消息模块:
- 新增模板消息支持
注意事项
- 显示操作的每一步结果，让用户了解进度
- 某个远程推送失败不影响其他远程的推送
- 禁止使用 git stash：本项目采用"先提交再拉取"策略
- 冲突标记搜索排除 node_modules 和 .git 目录
- 如果 Cursor 的 git 扩展已禁用（
git.enabled: false），请勿恢复，避免自动 stash 污染 index
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 · 95 lines · 0 tokens per session scan A b1e9fc901d65
Git提交和推送 is a command published in the GitHub repository nongjun/awesome-harness-engineering (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 864 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.