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/karashiiro/agent-skills/commit-stylenpx skills add karashiiro/agent-skills --skill commit-stylegit clone --depth 1 https://github.com/karashiiro/agent-skillsWrote 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/karashiiro/agent-skills/commit-style)<a href="https://agentmods.dev/skills/karashiiro/agent-skills/commit-style"><img src="https://agentmods.dev/badge/skills/karashiiro/agent-skills/commit-style.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.00611 |
| Opus 5 | $0.00032 | $0.00305 |
| Sonnet 5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Changes
Create a git commit using conventional commits format.
Commit Style
- Format:
type(scope): descriptionortype: description - Types:
feat,fix,docs,chore(minimal set) - Scope: Optional, use when it adds clarity (e.g.,
feat(auth):,fix(ipc):) - No AI attribution by default: Do not add "Generated with Claude Code" or Co-Authored-By lines unless required by the project standards (always check, first)
- No emojis: Keep messages plain text
Verbosity Rules
- Small changes (~1-4 files, simple modification): Title only, ~50-72 chars
- Medium changes (5-7 files, related modifications): Title + 1-3 sentence body
- Large changes (8+ files or significant feature): Title + bullet point list
Workflow
Note: For steps where it says to ask for directions, use your question tools, if available.
- Show current status: Run
git statusto see all changes - Show diff summary: Run
git diff --statfor overview,git difffor details if needed - Interactive staging: Ask which files/changes to include in this commit
- Draft message: Based on staged changes, draft a conventional commit message
- Review: Show the proposed message and ask for approval or edits
- Commit: Execute the commit (without --no-verify unless requested)
Instructions
Follow this workflow step by step. Be concise in your communication. When showing diffs, summarize large changes rather than dumping everything.
For the commit message:
- Use imperative mood ("Add feature" not "Added feature")
- First line should be under 72 characters
- If body is needed, separate from title with blank line
- Body lines should wrap at 72 characters
Example small commit:
docs: add design documentation index
Example medium commit:
feat(auth): implement OAuth token refresh
Add automatic token refresh when access token expires within 5 minutes.
Tokens are persisted to OS keychain via frontend IPC.
Example large commit:
docs: overhaul documentation
- Add cross-platform backend path resolution to frontend-architecture.md
- Clarify multi-turn conversation status in backend-adapter.md
- Create ROADMAP.md with phase breakdown
- Add asset authoring timeline to animation-system.md
- Create design docs index page
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.
- 3d ago First seen · 68 lines · 63 tokens per session scan A 94c8ba42b410
commit-style is a skill published in the GitHub repository karashiiro/agent-skills (2 stars, last pushed 4mo ago), licensed Unlicense. It adds 63 tokens to every session and 611 once invoked, about $0.0003 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
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…
commit
Create a signed git commit following Conventional Commits, after running /pre-commit and /changelog when appropriate.
commit
Read this skill before making git commits.
et-git
ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.