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.
git 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/plugins/nikeyes/stepwise-dev/git)<a href="https://agentmods.dev/plugins/nikeyes/stepwise-dev/git"><img src="https://agentmods.dev/badge/plugins/nikeyes/stepwise-dev/git/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/plugins/nikeyes/stepwise-dev/git"><img src="https://agentmods.dev/badge/plugins/nikeyes/stepwise-dev/git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stepwise-git 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
{
"name": "stepwise-git",
"version": "2.0.0",
"description": "Git and GitHub workflow: unattended commits, pull requests, CI checks and PR comment review",
"author": {
"name": "Jorge Castro",
"url": "https://github.com/nikeyes"
},
"homepage": "https://github.com/nikeyes/stepwise-dev",
"repository": "https://github.com/nikeyes/stepwise-dev",
"license": "Apache-2.0",
"keywords": [
"git",
"commit",
"version-control",
"pr",
"github",
"ci"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 127 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · +3 lines 49af3586a686
- 1mo ago Changed b5c53154fc21
- 1mo ago Changed d16f0ab756c0
- 1mo ago First seen · 18 lines scan A 3e0db4a1af1b
stepwise-git is a plugin published in the GitHub repository nikeyes/stepwise-dev (24 stars, last pushed 6d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
git
Git workflow automation (commit, PR, branching, changelog).
jj
Jujutsu (jj) version control skills for committing, pushing, opening PRs, and rebasing.
use-git
Apply git and GitHub CLI conventions for tmpfile bodies, signed commits and safe pushes, and create GitHub issues.
gitflow-cli
Gitflow CLI workflows and repository skills for Claude Code.