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 commands/dhofheinz/open-plugins/commit-splitgit clone --depth 1 https://github.com/dhofheinz/open-pluginsWhat 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.00009 | $0.05052 |
| Opus 5 | $0.00005 | $0.02526 |
| Sonnet 5 | $0.00002 | $0.01010 |
| Haiku 4.5 | $0.00001 | $0.00505 |
Grade A, and why
commit-split 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 — 836 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Split - Interactive Atomic Commit Creation
Overview
The /commit-split command provides an interactive workflow that orchestrates multiple skills to help you split large commits into focused, atomic commits. Each atomic commit represents one logical change that can be independently reviewed, tested, and reverted.
Skills Orchestrated
This command coordinates a complete execution workflow:
-
commit-error-handling - Pre-flight validation
- Operation:
/commit-error-handling diagnose-issues - Ensures: Repository ready for splitting
- Operation:
-
commit-analysis - Change understanding
- Operation:
/commit-analysis analyze - Provides: Type, scope, and file analysis for grouping
- Operation:
-
atomic-commit - Core splitting logic (PRIMARY)
- Operation:
/atomic-commit interactive - Provides: File grouping, suggestions, sequence generation
- This skill contains the core splitting algorithms
- Operation:
-
message-generation - Message creation
- Operation:
/message-generation complete(per commit) - Generates: Conventional commit message for each group
- Operation:
-
commit-best-practices - Quality assurance
- Operation:
/commit-best-practices check-pre-commit(optional) - Operation:
/commit-best-practices review-commit(after each) - Validates: Tests pass, quality maintained
- Operation:
-
history-analysis - Project awareness
- Operation:
/history-analysis analyze-style(cached) - Ensures: Messages match project conventions
- Operation:
Interactive Workflow
The /commit-split command provides a guided experience:
1. Analyze changes → Show plan
2. Group files → Present groups
3. For each group:
- Show files and changes
- Generate message
- Get user approval
- Create commit
- Review quality
4. Final summary
Alternative Workflows
For more control:
/atomic-commit interactive- Same workflow, skill-level access/atomic-commit sequence- Generate script to execute- Manual: Use
/commitfor each group after reviewing
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 · 836 lines · 9 tokens per session scan A 7b41ee7dd782
commit-split is a command published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 5,052 once invoked, about $0.0000 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 commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.