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.
git clone --depth 1 https://github.com/sorah/configWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/sorah/config/commit)<a href="https://agentmods.dev/commands/sorah/config/commit"><img src="https://agentmods.dev/badge/commands/sorah/config/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sorah/config/commit"><img src="https://agentmods.dev/badge/commands/sorah/config/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00012 | $0.00214 |
| Opus 5.5 | $0.00005 | $0.00086 |
| Sonnet 5.5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
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.
What it actually says
Load the commit-style skill and follow its conventions precisely — subject line style, prefix pattern, contextful verbs, lowercase imperative, and body guidelines.
Instructions
Review all staged and unstaged changes, then create git commit(s).
$ARGUMENTS
When argument contains "split"
Commit changes in logical, granular increments. Each commit should represent a single task or a functional unit. Ensure that the codebase remains stable and error-free at every commit point; do not commit code that is broken or fails to execute.
Before committing, present the proposed split plan (which files/hunks go into which commit, with draft subject lines) and wait for approval.
Otherwise
Commit all changes together in a single commit.
GPG Signing Errors
If a git commit fails with gpg: signing failed: Inappropriate ioctl for device, ask the user to unlock their signing key. Do not skip or disable GPG signing.
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 · 27 lines · 12 tokens per session scan A 8c9a9359afb7
commit is a command published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 214 once invoked, about $0.0000 per session on Opus 5.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-10-17.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.