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-stagednpx skills add jtsternberg/claude-plugins --skill commit-stagedgit 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.00027 | $0.00315 |
| Opus 5 | $0.00014 | $0.00158 |
| Sonnet 5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
commit-staged 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 2d 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 Changes
Use this skill only when the user explicitly asks to commit their staged 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. - Stop if there are no staged changes. Do not create an empty commit.
- 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). - Check that the staged files do not include secrets or private configuration (for example
.env, credential files, tokens, or private keys). Stop and tell the user if they do. - Create the commit from the staged files. Do not amend, use
--no-verify, or push unless the user explicitly asks. - Report the commit hash and the remaining
git statusstate.
If the staged diff contains unrelated changes, stop before committing and ask the user to split or clarify the intended scope.
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.
- 2d ago First seen · 27 lines · 27 tokens per session scan A 50fad10cb439
commit-staged is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 315 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…
commit
Commit message formatting and guidelines.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
git-commit
Generate well-formatted git commit messages following conventional commit standards.