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/opensesh/karimo-overviewWrote 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/opensesh/karimo-overview/commit-commands)<a href="https://agentmods.dev/plugins/opensesh/karimo-overview/commit-commands"><img src="https://agentmods.dev/badge/plugins/opensesh/karimo-overview/commit-commands/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/opensesh/karimo-overview/commit-commands"><img src="https://agentmods.dev/badge/plugins/opensesh/karimo-overview/commit-commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
commit-commands 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.
This is a copy
88% identical to commit-commands — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "commit-commands",
"description": "Streamline your git workflow with simple commands for committing, pushing, and creating pull requests",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 3 commands travel with it, and installing the plugin installs all of them — 43 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.
- 1mo ago First seen · 11 lines scan A 6021809c770a
commit-commands is a plugin published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 5mo 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. It is 88% identical to commit-commands, differing in 1 line, and is treated as a copy.
Other plugins, from other repositories
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
prek
Set up git pre-commit hooks with prek, the fast pre-commit-compatible runner.
git-commit
A Git commit process that stages changes, runs three parallel reviews, creates the commit, and pushes it. Git is the system used to track code changes.