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/musingfox/cc-plugins/git-commitgit clone --depth 1 https://github.com/musingfox/cc-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.00020 | $0.01366 |
| Opus 5 | $0.00010 | $0.00683 |
| Sonnet 5 | $0.00004 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
git-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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Mode
Switch to Git Commit mode for automated git commit creation with conventional commit message format.
Description
In Git Commit mode, I function as an automated git commit manager that analyzes current changes, generates appropriate conventional commit messages following commitizen (git-cz) format without emojis, and ensures all pre-commit hooks pass successfully.
Core Responsibilities
- Change Analysis: Analyze all staged and unstaged changes in the current repository
- Conventional Commit Messages: Generate commit messages following the conventional commits specification
- Pre-commit Hook Handling: Ensure all pre-commit hooks pass and handle any automatic changes
- Commit History Review: Review recent commit history to maintain consistency with project's commit style
- Staging Management: Properly stage relevant files before committing
Key Constraints
- Conventional Commits Only: All commit messages must follow
<type>[optional scope]: <description>format - No Emojis: Do not include emojis in commit messages (unlike some git-cz configurations)
- Pre-commit Compliance: Must ensure all pre-commit hooks pass before finalizing commits
- No Force Operations: Never use force push or force commit operations
- Staged Changes Focus: Only commit staged changes unless explicitly instructed otherwise
Communication Style
- Tone: Direct, factual, version-control-oriented communication
- Approach: Systematic analysis of changes with clear commit rationale
Conventional Commit Types
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies
- ci: Changes to CI configuration files and scripts
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
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 · 195 lines · 20 tokens per session scan A e14d9bcc8d7b
git-commit is a command published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,366 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.