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 skills add sorah/config --skill commit-stylegit 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/skills/sorah/config/commit-style)<a href="https://agentmods.dev/skills/sorah/config/commit-style"><img src="https://agentmods.dev/badge/skills/sorah/config/commit-style/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/skills/sorah/config/commit-style"><img src="https://agentmods.dev/badge/skills/sorah/config/commit-style.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.00068 | $0.01303 |
| Opus 5.5 | $0.00027 | $0.00521 |
| Sonnet 5.5 | $0.00014 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
commit-style 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Style
Conventions for writing git commit messages and pull request descriptions. Project-specific conventions always take priority.
Subject Line
- Try to keep under 50 characters total
- No trailing period
- Lowercase imperative verbs:
fix,add,remove,use,avoid,ensure,adjust,allow,enable,extract,introduce,show,move,roll - Capital letter only when starting with a proper noun or class name — never capitalize verbs
- Embed the "why" directly when possible:
avoid enlarging small images,avoid double-save on withdraw - Technical identifiers kept verbatim:
config.x.asset_file_uploadable,event_submission_open? - Arrow notation for renames:
ops-lb: rknw -> rknet
Keeping Under 50 Characters
Techniques when the subject runs long:
- Drop
addwhen the subject already names the primary new thing:site-sessions: SiteSession modelnot… add SiteSession model— keepaddwhen supplementing existing code (specs, logging) - Omit secondary artifacts when the primary deliverable is clear:
site-sessions: SiteSessionIssuance servicenot… service and background jobs— mention omitted parts in the body &overand:PrimarySession & User changes- Drop qualifiers the prefix already provides:
site-sessions: PrimarySession & User changesnot… for site sessions
Contextful Verbs
Prefer specific verbs over generic ones:
avoidoraddressoverfixfor preventive changesextractoverrefactorwhen pulling out a concern/classintroduceoveraddwhen creating a new concept/abstractionreflectoverupdatewhen syncing with external stategainsfor new capabilities (component as subject):SponsorEvent: gains hero image uploadlearnsfor new options/parameters:TitoApi: learns v3.1 paginationno longerfor behavioral removals:event_submission_open? no longer gates asset uploadsrollfor dependency updates and referenced image/git tag updates,relengfor release engineering,triggerfor CI/build triggersrollis short for "roll out": the object is what gets rolled, followed directly by the version, neverto:roll sorah/glazed 0.3.0,roll himari-lambda image 5b9d6b9, notroll image to 0.3.0
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 · 103 lines · 68 tokens per session scan A 0a37417f6ac7
commit-style is a skill published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,303 once invoked, about $0.0003 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 skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
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.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.