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 skills add qte77/claude-code-plugins --skill committing-staged-with-messagegit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/qte77/claude-code-plugins/committing-staged-with-message)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/committing-staged-with-message"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/committing-staged-with-message/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/committing-staged-with-message"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/committing-staged-with-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00034 | $0.00473 |
| Opus 5.5 | $0.00014 | $0.00189 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
committing-staged-with-message 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 1mo ago.
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.
What it actually says
Commit staged with Generated Message
Step 1: Analyze Staged Changes
Run these commands using the Bash tool to gather context:
git diff --staged --name-only- List staged filesgit diff --staged --stat- Diff stats summarygit log --oneline -5- Recent commit stylegit diff --staged- Review detailed staged changes. Size guard: if--statshows >10 files or >500 lines changed, skip the full diff and rely on--stat+--name-onlyto generate the message.
Step 2: Generate Commit Message
Use the Read tool to check .gitmessage for commit message format and syntax.
The commit message body MUST include (concisely — no padding, no redundancy):
- What changed: bullet points per file or logical group
- Symbols added/removed (when applicable): functions, classes, tests
- Diff stats: lines added/removed (from
--statsummary line) — MUST be the last line of the body- Format:
+ symbol_name,- symbol_name - Omit for config/docs/formatting-only changes
- Format:
Keep the message laser-focused. Do not repeat the subject line in the body.
Step 3: Pause for Approval
Please review the commit message.
- Approve: "yes", "y", "commit", "go ahead"
- Edit: Provide your preferred message
- Cancel: "no", "cancel", "stop"
Step 4: Commit
Once approved:
git commit --gpg-sign -m "[message]"- Commit staged changes with approved message (GPG signature mandatory)git status- Verify success
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.
- 1mo ago First seen · 51 lines · 34 tokens per session scan A 7bd4fb38382a
committing-staged-with-message is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 34 tokens to every session and 473 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
smart-commit
Create clean Conventional Commits: inspect the diff, group related changes, run quality checks, and write type(scope) messages. Use when committing work, or when the user runs /smart-commit or asks to commit changes.
feature-flow
Complete git workflow orchestration (GitHub/GitLab/Forgejo) - branch, issue, commit.
dream
Check this project's memory notes against the repo, fix the ones that went false, and tidy the index, as one git commit you can revert. Checks only notes that are new or name a changed file; pass all to check every note. Costs one Sonnet call per 15 notes, plus one.
commit
Create conventional commit from staged changes with approval.
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…