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/commitshow/cliWrote 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/commitshow/cli/cli)<a href="https://agentmods.dev/plugins/commitshow/cli/cli"><img src="https://agentmods.dev/badge/plugins/commitshow/cli/cli/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/commitshow/cli/cli"><img src="https://agentmods.dev/badge/plugins/commitshow/cli/cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
commitshow 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 13d 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": "commitshow",
"displayName": "commit.show audit",
"version": "0.1.1",
"description": "Score any public GitHub repo 0-100 against the commit.show audit rubric — Lighthouse, repo signals, security, surfaced as paste-ready markdown inside Cursor.",
"author": {
"name": "commit.show",
"email": "[email protected]"
},
"homepage": "https://commit.show",
"repository": "https://github.com/commitshow/cli",
"license": "MIT",
"keywords": [
"audit",
"code-quality",
"lighthouse",
"github",
"vibe-coding",
"mcp",
"claude",
"cursor"
],
"category": "developer-tools",
"tags": [
"audit",
"code-quality",
"github",
"vibe-coding"
],
"mcp": "./mcp.json"
}
What it installs
The manifest is a name and a version. 2 MCP servers travel with it, and installing the plugin installs all of 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.
- 13d ago First seen · 32 lines scan A 3bfb01a7a935
commitshow is a plugin published in the GitHub repository commitshow/cli (1 stars, last pushed 14d ago), licensed MIT. 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-09-23.
Other plugins, from other repositories
aigon
aigon. Aigon is a local, open-source, spec-first software-delivery orchestrator for coding agents. It takes a Git-backed feature spec through isolated implementation, cross-agent review, and merge—using the agents and subscriptions you already have.
skillreaper
Measures what share of your agent's loaded context is ever actually invoked - skills, MCP servers, subagents, hooks, always-loaded prose - using evidence from your own session transcripts. Then prunes the dead weight, reversibly.
fettle
In-session quality governance for AI-assisted development, with advisory-first code and process gates, evidence, and multi-agent controls.
seqwalk
Walk through AI-written code with interactive HTML sequence diagrams.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.