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/magic3007/dotfiles/scan-commitnpx skills add magic3007/dotfiles --skill 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.00035 | $0.02378 |
| Opus 5 | $0.00017 | $0.01189 |
| Sonnet 5 | $0.00007 | $0.00476 |
| Haiku 4.5 | $0.00003 | $0.00238 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 304 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 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
Invoke with /scan-commit or when the task matches.
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.
- 2d ago First seen · 304 lines · 35 tokens per session scan A e5e48d93db96
scan-commit is a skill published in the GitHub repository magic3007/dotfiles (10 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 2,378 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 skills, from other repositories
assess-quality
Foundational quality framework: the five questions (readable, easy to start, expands without bloat, consistent, intentional) every other dev skill is judged against, plus the dual-audience and workshop principles. Use when onboarding to a project, defining a quality bar, setting an assessment checklist, or arbitrating…
create-oss-skill
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
orchestrate-agents
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel…
extend-oss-skills-to-claude
Extend standard agentskills.io skills with Claude Code-specific features. Invocation control, subagent execution, dynamic context injection, string substitutions, model/effort overrides, and deployment scoping. Use when adapting a portable skill for Claude Code, adding Claude-specific frontmatter, setting up subagent…
merge-ready
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness…
scaffold-project
Generates cross-language standard files (README, AGENTS.md, LICENSE, CONTRIBUTING.md, SECURITY.md, sr.yaml, .envrc, llms.txt), documentation conventions, and project structure, then dispatches to language-specific scaffolds. Use first for cross-language standard files and structure, THEN load the matching scaffold…