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/commitgit 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.00011 | $0.04772 |
| Opus 5 | $0.00005 | $0.02386 |
| Sonnet 5 | $0.00002 | $0.00954 |
| Haiku 4.5 | $0.00001 | $0.00477 |
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 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 — 656 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligent Git Commit Assistant
Create well-formatted git commits with optional automatic message generation following conventional commits standards.
Overview
The /commit command provides a simplified workflow that orchestrates multiple specialized skills to create intelligent, well-formatted commits following conventional commits standards.
Skills Orchestrated
This command coordinates these granular skills:
-
commit-error-handling - Validates git repository state and checks for issues
- Operation:
/commit-error-handling diagnose-issues - Purpose: Ensure repository is in a clean state before committing
- Operation:
-
commit-analysis - Analyzes changes to determine type, scope, and atomicity
- Operation:
/commit-analysis analyze - Purpose: Understand what changes are being committed
- Operation:
-
history-analysis (optional) - Learns project commit conventions
- Operation:
/history-analysis analyze-style - Purpose: Match team's existing commit style
- Operation:
-
commit-best-practices - Validates commit readiness
- Operation:
/commit-best-practices check-pre-commit - Purpose: Ensure tests pass, no debug code, lint clean
- Operation:
-
message-generation - Generates conventional commit messages
- Operation:
/message-generation complete - Purpose: Create well-formatted conventional commit message
- Operation:
-
atomic-commit (conditional) - Suggests splitting if needed
- Operation:
/atomic-commit analyze - Purpose: Determine if changes should be split into multiple commits
- Operation:
For Granular Control
If you need precise control over individual operations:
- Use
/commit-error-handlingfor error diagnosis - Use
/commit-analysisfor change analysis - Use
/message-generationfor message generation - Use
/atomic-commitfor commit splitting - Use
/commit-best-practicesfor validation - Use
/history-analysisfor project conventions
See the commit-assistant agent for complete skill documentation.
Usage
/commit # Analyze changes and generate commit message
/commit "feat: add login" # Use provided message directly
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 · 656 lines · 11 tokens per session scan A 6e4a3eea6ed2
commit is a command published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 4,772 once invoked, about $0.0001 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.