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 nikeyes/stepwise-dev --skill commitgit clone --depth 1 https://github.com/nikeyes/stepwise-devWrote 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/nikeyes/stepwise-dev/commit)<a href="https://agentmods.dev/skills/nikeyes/stepwise-dev/commit"><img src="https://agentmods.dev/badge/skills/nikeyes/stepwise-dev/commit/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/nikeyes/stepwise-dev/commit"><img src="https://agentmods.dev/badge/skills/nikeyes/stepwise-dev/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00449 |
| Opus 5.5 | $0.00006 | $0.00180 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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 8d 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 Changes
Create git commit(s) for the uncommitted changes in the working tree. Do not ask for confirmation: decide, commit, then report what you committed.
Rules
- Format:
TYPE([SCOPE])[!]: description(e.g.feat(kyc): add disapproval reason to kyc mail)- Types:
feat,fix,refactor,perf,style,test,docs,build,ops,chore,revert,reapply - Scope: optional, contextual (never a ticket id)
- Breaking change:
!before:, or aBREAKING CHANGES:footer - Description: imperative present tense, lowercase, no trailing period
- Body/footer: optional; use to explain motivation and contrast with previous behavior
- Types:
- Splitting: group related changes; multiple commits if the changes have distinct purposes
- Staging:
git addeach file by name, never-Aor.. Stage every modified or new file that belongs to the work. Leave out anything that looks like a secret (.env, keys, credentials), a large binary or a generated artifact. - Never include: ticket identifiers (Jira, Linear, etc.), Claude attribution,
Co-Authored-Bylines - Nothing to commit: say so and stop.
- Report: the commits you created (hash and subject) and every file you left out, with the reason.
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.
- 8d ago Changed · +1 lines · -2 tokens per session 41424c5b87b1
- 1mo ago Changed 69a7b81b51d4
- 1mo ago Changed a46afe919daf
- 1mo ago First seen · 29 lines · 17 tokens per session scan A cc79f162259c
commit is a skill published in the GitHub repository nikeyes/stepwise-dev (24 stars, last pushed 6d ago), licensed Apache-2.0. It adds 15 tokens to every session and 449 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.