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/javiermrcom/awesome-claude-code/commitgit clone --depth 1 https://github.com/javiermrcom/awesome-claude-codeWhat 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.00019 | $0.01284 |
| Opus 5 | $0.00010 | $0.00642 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00128 |
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Commit Command
This command enhances Claude Code's native commit abilities by:
- Analyzing ALL changes (staged + unstaged) to find logical groupings
- Intelligently staging/unstaging files to create atomic commits
- Generating Conventional Commits format messages WITHOUT attribution
- Auto-detecting and referencing Linear issues and Sentry errors from context
Core Logic
The command will:
- Assess what's currently staged vs unstaged
- Use conversation context OR change analysis to group related files
- Detect Linear issues and Sentry errors from session context
- Stage the right files for a single logical commit
- Generate a proper Conventional Commits message with issue references
Task
Analyze the current git state and conversation context. Based on this:
-
Analyze Git State:
- Run
git status --porcelainto see all changes - Determine what forms a logical unit based on:
- Conversation context (if available)
- File relationships (source + tests, docs together, etc.)
- Run
-
Detect Issue References:
- Linear Issues: Scan conversation for Linear issue IDs (e.g., IA-123, ENG-456)
- Sentry Issues: Detect Sentry error references (e.g., ABCD-7S, issue IDs, URLs)
- Priority: Use the most relevant issue mentioned in current conversation context
-
Stage Changes:
- Unstage files that don't belong in this commit
- Stage files that complete the logical change
-
Generate Commit Message:
- Follow Conventional Commits format
- Include issue references in footer when detected
- Format:
Refs: IA-123(Linear) orFixes: ABCD-7S(Sentry) or both
-
Execute Commit
Commit Message Format (Conventional Commits v1.0.0):
<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]
Body Guidelines:
- Include a body for non-trivial changes (most commits should have one)
- Use bullet points with
-prefix (3-5 lines typical) - Each bullet should describe a specific aspect of the change
- Keep each bullet concise and focused
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 · 165 lines · 19 tokens per session scan A 9bab3c244349
commit is a command published in the GitHub repository javiermrcom/awesome-claude-code (3 stars, last pushed 10mo ago), licensed MIT. It adds 19 tokens to every session and 1,284 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.