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/kossakovsky/cc-plugins/commitgit clone --depth 1 https://github.com/kossakovsky/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.00010 | $0.00549 |
| Opus 5 | $0.00005 | $0.00275 |
| Sonnet 5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Git Commit
Create a git commit with a conventional commit message, either provided or auto-generated.
Steps
-
Check for provided message: If an argument was provided, use it as the commit message directly and skip to step 6.
-
Check working tree state: Run
git statusto see the current state of the repository. -
Handle staging:
- If nothing is staged, show the unstaged changes and ask the user what to stage.
- Suggest
git add -Ato stage everything, or let the user specify individual files. - Never stage files without explicitly showing what will be staged and getting confirmation.
-
Analyze staged changes: Run
git diff --stagedto understand what has been changed. -
Detect project commit style: Run
git log --oneline -10to see recent commit messages and adapt to the project's conventions. -
Determine change type: Analyze the diff to classify the change as one of:
feat— new featurefix— bug fixrefactor— code restructuring without behavior changedocs— documentation onlychore— maintenance, dependencies, configtest— adding or updating testsstyle— formatting, whitespace, lintingperf— performance improvementci— CI/CD configurationbuild— build system or external dependencies
-
Generate commit message: Create a message following the conventional commit format:
type(scope): description- type: determined from the diff analysis above
- scope: optional, inferred from the changed files or directories
- description: concise summary of changes in imperative mood (e.g., "add user auth endpoint", not "added user auth endpoint")
-
Present for approval: Show the generated commit message and ask the user to approve, edit, or reject it.
-
Execute commit: If approved, run
git commit -m "<message>". -
Show result: Display the commit output to confirm success.
Important Rules
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 · 56 lines · 10 tokens per session scan A 8746f9cec730
commit is a command published in the GitHub repository kossakovsky/cc-plugins (3 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 549 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.