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 skills/u9401066/asset-aware-mcp/git-precommitnpx skills add u9401066/asset-aware-mcp --skill git-precommitgit clone --depth 1 https://github.com/u9401066/asset-aware-mcpWhat 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.00060 | $0.00678 |
| Opus 5 | $0.00030 | $0.00339 |
| Sonnet 5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
git-precommit 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 2d 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.
This is a copy
100% identical to git-precommit — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Git 提交前工作流（編排器）
描述
協調多個 Skills 完成 Git 提交前的所有準備工作。
觸發條件
- 「準備 commit」「要提交了」「git commit」
法規依據
- 憲法：CONSTITUTION.md 第三章
- 子法：.github/bylaws/git-workflow.md
執行流程
┌─────────────────────────────────────────────────┐
│ Git Pre-Commit Orchestrator │
├─────────────────────────────────────────────────┤
│ Step 1: memory-sync [必要] Memory Bank 同步 │
│ Step 2: readme-update [可選] README 更新 │
│ Step 3: changelog-update[可選] CHANGELOG 更新 │
│ Step 4: roadmap-update [可選] ROADMAP 更新 │
│ Step 5: arch-check [條件] 架構文檔檢查 │
│ Step 6: commit-prepare [最終] 準備提交 │
└─────────────────────────────────────────────────┘
參數
| 參數 | 說明 | 預設 |
|---|---|---|
--skip-readme |
跳過 README 更新 | false |
--skip-changelog |
跳過 CHANGELOG 更新 | false |
--skip-roadmap |
跳過 ROADMAP 更新 | false |
--dry-run |
只預覽不修改 | false |
--quick |
只執行必要步驟 (memory-sync) | false |
使用範例
「準備 commit」 # 完整流程
「快速 commit」 # 等同 --quick
「commit --skip-readme」 # 跳過 README
輸出格式
🚀 Git Pre-Commit 工作流
[1/6] Memory Bank 同步 ✅
└─ progress.md: 更新 2 項
└─ activeContext.md: 已更新
[2/6] README 更新 ✅
└─ 新增功能說明
[3/6] CHANGELOG 更新 ✅
└─ 添加 v0.2.0 條目
[4/6] ROADMAP 更新 ⏭️ (無變更)
[5/6] 架構文檔 ⏭️ (無結構性變更)
[6/6] Commit 準備 ✅
└─ 建議訊息：feat: 新增用戶認證模組
📋 Staged files:
- src/auth/...
- docs/...
準備好了！確認提交？
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.
- 2d ago First seen · 79 lines · 60 tokens per session scan A 461fd22ef4ec
git-precommit is a skill published in the GitHub repository u9401066/asset-aware-mcp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 60 tokens to every session and 678 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-precommit, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
git-doc-updater
Skill "git-doc-updater" from u9401066/HyperHierarchicalRAG, covering git 文檔自動更新技能, 描述, 觸發條件, 自動更新的文檔 and 1. readme.md.
git-precommit
Skill "git-precommit" from u9401066/HyperHierarchicalRAG, covering git 提交前工作流（編排器）, 描述, 觸發條件, 法規依據 and 執行流程.
doc-traceability-validator
Validate documentation traceability between code annotations (@implements), feature registry, business rules, and use cases. Detect ID collisions, undocumented features, broken cross-references, and namespace violations.
langfuse
Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any…
makefile-dev-workflow
Unified development workflow for EdgeQuake using Makefile commands. Use when starting services, running tests, or managing the full development stack (database, backend, frontend). Provides simplified alternatives to raw cargo/npm commands.
reverse-documentation
Automatically generate comprehensive documentation for Rust and TypeScript codebases by analyzing code structure, patterns, and relationships. Supports trait-based patterns, async operations, React components, and Next.js applications.