Borrowing it
Nothing to install: this file belongs to benoror/obsidianos_work. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/benoror/obsidianos_work/main/.agents/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/benoror/obsidianos_workWrote 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/benoror/obsidianos_work/commit)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/commit"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/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/skills/benoror/obsidianos_work/commit"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/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.00027 | $0.01355 |
| Opus 5.5 | $0.00011 | $0.00542 |
| Sonnet 5.5 | $0.00005 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Usage
| Command | What it does |
|---|---|
/commit |
Commit staged files; if none staged, infer related changes |
/commit <file> |
Scope to a specific file's changes |
/commit <folder>/ |
Scope to a folder's changes |
/commit <description> |
Infer scope from free-text intent |
/commit <scope> <description> |
Scope + explicit intent |
/commit amend |
Amend the last commit (re-use message) |
/commit amend <scope/description> |
Amend with additional scope or new message |
| (sequence mode) | Deferred — sub-skills skip, caller commits once at the end |
Argument Parsing
Parse the raw argument string into scope, intent, and flags:
- Amend flag: If the first word is
amend, set amend mode and strip it. The remainder is parsed normally. - Scope (file or folder): Any token that matches a real path in the repo (file or directory) — whether provided via
@-reference or plain text. Multiple scopes are allowed. - Intent (free-text description): Whatever remains after extracting scopes. Used to guide the commit message.
- Nothing: No arguments at all — default mode.
Examples:
| Input | Scope | Intent | Amend |
|---|---|---|---|
| (empty) | — | — | no |
Meetings/Engineering/ |
Meetings/Engineering/ |
— | no |
.gitignore |
.gitignore |
— | no |
my awesome refactor |
— | my awesome refactor |
no |
Meetings/ wrap up notes |
Meetings/ |
wrap up notes |
no |
amend |
— | — | yes |
amend .obsidian/ |
.obsidian/ |
— | yes |
amend fixed typo |
— | fixed typo |
yes |
Workflow
1. Gather state
Run in parallel:
git diff --staged --stat— staged changesgit diff --stat— unstaged changesgit status --short— untracked filesgit log --oneline -5— recent commits (for style and amend safety)
2. Determine file set
Resolve which files will be committed, based on parsed arguments:
| Scenario | File set |
|---|---|
| Scope provided | Only changed/untracked files under the given path(s). Ignore everything else. |
| Intent provided, no scope | Analyze all changed files; select only those whose diffs relate to the described intent. Present the selection for confirmation. |
| No args + staged files exist | Use exactly what's staged. Do NOT add unstaged files — the user intentionally staged those. |
| No args + nothing staged | Analyze all changed/untracked files. Group related changes and propose a sensible set. Ask for confirmation. |
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.
- 1mo ago First seen · 129 lines · 27 tokens per session scan A e96e99f19497
commit is a skill published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 1,355 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
to-code
Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
polya-code
Phase 3 of the Pólya Heuristic Coder: Carrying Out the Plan, Clean Architecture Seams, Two-Layer Testing Mandate, Inductive Verification, Floor-Guard Anti-Cheat, and Atomic Conventional Commits.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.