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 skills/jtsternberg/claude-plugins/commit-unstagednpx skills add jtsternberg/claude-plugins --skill commit-unstagedgit clone --depth 1 https://github.com/jtsternberg/claude-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.00028 | $0.00350 |
| Opus 5 | $0.00014 | $0.00175 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
commit-unstaged 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 3d 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 Unstaged Changes
Use this skill only when the user explicitly asks to stage and commit their current changes.
Arguments provided: $ARGUMENTS
Codex: if the invocation text above is not populated, use a commit message supplied after the skill name or in the current request. If none is available, infer the message from the diff.
Workflow
- Inspect the repository state with
git status,git diff, andgit diff --cached. - Identify the files that belong in this commit. Do not use
git add -Aorgit add .; stage each intended file by explicit path. - Stop if the intended files include secrets or private configuration (for example
.env, credential files, tokens, or private keys). Do not stage them. - Review the staged diff. If it contains unrelated changes, unstage the unrelated paths or ask the user to split the work before committing.
- Respect a commit message supplied by the user. Otherwise, derive a concise conventional commit message from the staged diff and the repository's recent commit style (
git log). - Create the commit. Do not amend, use
--no-verify, or push unless the user explicitly asks. - Report the commit hash and the remaining
git statusstate.
If there are no unstaged changes, say so and do not create an empty commit.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 28 lines · 28 tokens per session scan A 462449f482dd
commit-unstaged is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 350 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 skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…