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/magic3007/dotfiles/scan-commitgit clone --depth 1 https://github.com/magic3007/dotfilesWhat 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.00042 | $0.02527 |
| Opus 5 | $0.00021 | $0.01264 |
| Sonnet 5 | $0.00008 | $0.00505 |
| Haiku 4.5 | $0.00004 | $0.00253 |
Grade A, and why
scan-commit 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.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan Commit
Scan the entire working tree for pending changes — unstaged modifications, untracked files, and (with a warning) already-staged changes — analyze them into logical groups at the hunk level, then stage and commit each group with well-structured messages following Conventional Commits v1.0.0.
This command extends the /smart-commit workflow by adding the scanning and staging phases. It handles the common case where a developer has been working on multiple concerns and hasn't staged anything yet.
Usage
/scan-commit [--dry-run]
Arguments:
--dry-run: Only show the proposed commit plan without executing
Workflow
Step 1: Scan All Changes
# Unstaged modifications to tracked files
git diff --no-color
# Untracked new files
git status --porcelain
# Already-staged changes (warn if present)
git diff --cached --stat
Collect three categories of changes:
| Category | Command | Description |
|---|---|---|
| Modified (unstaged) | git diff --no-color |
Changes to tracked files not yet staged |
| Untracked | git status --porcelain |
New files git doesn't know about |
| Staged | git diff --cached --stat |
Already staged (warn, include in analysis) |
If no changes exist at all, stop and inform the user.
If there are already-staged changes, warn the user. Include them in the analysis but note they are already staged — they will be committed as-is (no hunk splitting on already-staged content).
Step 2: Read and Understand All Changes
For each changed file, understand:
- What was added, modified, or deleted
- How the change relates to other files
- For files with multiple logical changes (e.g., a bug fix AND a refactor in the same file), identify each hunk's purpose
Use git diff --no-color output to analyze at the hunk level. Each hunk starts with @@ ... @@ and represents a contiguous block of change. Determine which hunks belong together logically.
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 · 313 lines · 42 tokens per session scan A 8312584df22f
scan-commit is a command published in the GitHub repository magic3007/dotfiles (10 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 2,527 once invoked, about $0.0002 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-31.
Other commands, from other repositories
spec
Command "spec" from xiongchenyu6/dotfiles, covering 1. 先自查,再问人, 2. 一次问完, 3. 输出 spec 并等我确认, 退出条件 and 确认之后.
issue-implement
Pick up GitHub issue $ARGUMENTS.
pr
Create a GitHub PR from the current repo changes.
push-commit
Create a new commit from the current repo changes and push it.
commit
Create a new commit from the current repo changes.
pr-address-reviews
Address unresolved review comments on PR $ARGUMENTS.