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/yegor256/courier/commit-changes-to-gitnpx skills add yegor256/courier --skill commit-changes-to-gitgit clone --depth 1 https://github.com/yegor256/courierWhat 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.00028 | $0.00307 |
| Opus 5 | $0.00014 | $0.00153 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
commit-changes-to-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 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.
What it actually says
Scope
Operate on Git repository in current working directory. Refuse to bundle unrelated changes into one commit.
Boundaries
Commit files untouched, never reformatting, linting, testing, or building. Honor hooks and signing unless user asked to bypass them. Land one local commit, never amending, rebasing, force-pushing, or pushing.
Staging
Stage only paths user named, or everything when user said so. Refuse to stage secrets. Warn user about skipped secrets instead.
Message
Respect Conventional Commits standard.
Prepend ticket number to description with # when user named issue.
Derive message from diff and conversation, never from branch name.
Format
Shape commit as type: summary subject, then optional body.
Review
List staged files for user before committing. Show commit subject to user before committing.
Authorship
Limit message to its description.
Skip Co-authored-by: trailers, promotional lines, signatures, and emoji.
Preserve configured author and committer identity.
Example
User fixes typo in README.md and says "commit it".
Stage README.md alone.
Write subject docs: fix typo in README.
Land one commit carrying that subject.
Done
Confirm one new commit appears after run. Stop after single commit lands.
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 · 57 lines · 28 tokens per session scan A 2abfd23b4b12
commit-changes-to-git is a skill published in the GitHub repository yegor256/courier (3 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 307 once invoked, about $0.0001 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
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
ac-commit-manager
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
update-pr-summary
This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".
om-auto-continue-pr-loop
Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and checkpoint discipline (integration tests + screenshots for UI), runs the full gate at completion, keeps spec-only design PRs…
om-open-pr
Shared PR opener for the auto pipeline — commits the worktree, pushes, reuses an existing PR or opens a ready (non-draft) PR against the configured base branch with the unified body template, applies the full SDLC label set with rationale comments, and for issue-driven runs hands the issue back and releases the lock.…