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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/commit)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/commit"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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/yonatangross/orchestkit/commit"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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.00087 | $0.02631 |
| Opus 5.5 | $0.00035 | $0.01052 |
| Sonnet 5.5 | $0.00017 | $0.00526 |
| Haiku 4.5 | $0.00009 | $0.00263 |
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 17d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/commit/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Smart Commit
Host-neutral workflow. Invoke by skill name (commit). Claude Code slash routing, YAML hook loaders, and .claude/chain live in skills/commit/references/claude-code.md.
Simple, validated commit creation. Run checks locally, no agents needed for standard commits.
Note: If
disableSkillShellExecutionis enabled (CC 2.1.91), the git repository check won't run. This skill requires a git repository.
Quick Start
commit
commit fix typo in auth module
Argument Resolution
COMMIT_MSG = "$ARGUMENTS" # Optional commit message, e.g., "fix typo in auth module"
# If provided, use as commit message. If empty, generate from staged changes.
# $ARGUMENTS[0] is the first token (CC 2.1.59 indexed access)
STEP 0: Choose Commit Mode (AskUserQuestion — M118 #1465)
Default is "new commit", but voice-flow needs explicit choice when amend / push / stash is wanted:
# Skip when a flag in the invocation makes the mode unambiguous:
# commit --amend → skip, mode=amend
# commit --push → skip, mode=new+push
# commit --stash → skip, mode=stash-first
# ORK_COMMIT_DEFAULT_MODE=new (or amend|push|stash) → skip, use env value
#
# Otherwise, ask:
AskUserQuestion(questions=[{
"question": "How should this commit land?",
"header": "Commit mode",
"options": [
{"label": "New commit (default)", "description": "Create a new commit, leave HEAD intact"},
{"label": "Amend HEAD", "description": "Fold staged changes into the last commit (LOCAL ONLY — refuses if HEAD is published)"},
{"label": "New commit + push", "description": "Commit then `git push` (refuses on protected branches)"},
{"label": "Stash first", "description": "Stash unrelated working-tree changes, then commit only what was already staged"}
]
}])
Mode-specific guards:
- Amend HEAD — verify HEAD is not on origin (
git rev-list HEAD..origin/<branch>empty); if it is published, refuse and recommend "New commit" instead. - New commit + push — re-check the protected-branch rule from Phase 1 before pushing; if HEAD's branch is
main/master/dev, abort. - Stash first —
git stash push -k -m "ork:commit autostash"(keep-index), commit, thengit stash popafter push success.
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.
- 17d ago Changed 1d12dfcb8e2c
- 22d ago Changed · -22 tokens per session 8960101b6066
- 1mo ago Changed · +13 lines · +18 tokens per session 20ac76031826
- 1mo ago Changed · +2 lines 5c20c5664aa7
- 1mo ago Changed 36483654405a
- 1mo ago First seen · 236 lines · 91 tokens per session scan A baf8a7a016eb
commit is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 2,631 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-08-30.
Other commands, from other repositories
quick-push
Git add all, commit with Claude, and push to current/new feature branch.
new-feature-branch
Branch-from-fresh-main boilerplate — checkout main, pull, create branch with a meaningful name, push empty so it can be protected.
speckit.git.initialize
Initialize a Git repository with an initial commit.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.