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/gowtham012/Claude-pluginsWrote 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/gowtham012/claude-plugins/diff-narrator)<a href="https://agentmods.dev/plugins/gowtham012/claude-plugins/diff-narrator"><img src="https://agentmods.dev/badge/plugins/gowtham012/claude-plugins/diff-narrator/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/gowtham012/claude-plugins/diff-narrator"><img src="https://agentmods.dev/badge/plugins/gowtham012/claude-plugins/diff-narrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
diff-narrator 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.
What it actually says
{
"name": "diff-narrator",
"description": "After every edit, generates a plain-English summary of what changed and why. Maintains a running changelog and produces PR-ready descriptions.",
"version": "1.0.0",
"author": {
"name": "Gowtham"
},
"license": "MIT",
"homepage": "https://github.com/gowtham012/Claude-plugins/tree/main/diff-narrator",
"repository": "https://github.com/gowtham012/Claude-plugins",
"keywords": [
"changelog",
"diff",
"narration",
"pr-description",
"documentation"
]
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 54 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 1mo ago First seen · 18 lines scan A 073eb4291f74
diff-narrator is a plugin published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 7mo 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-08-31.
Other plugins, from other repositories
cadence
A plan/execute/verify loop for a single developer in Claude Code, with adversarial review at every gate: plans and diffs get refuted by a fresh Claude subagent or a panel of outside models (OpenAI, Gemini, DeepSeek), not just approved. State lives in files, not the conversation, so you clear aggressively and keep both.
software-factory
Lanes, tickets, and a human merge. Same skills as Cursor, Grok, and Codex.
agile-ledger
Plain-Markdown Scrum/Agile product management for Claude Code — backlog, sprints, board, velocity, releases, and GitHub traceability from slash commands. The ledger lives in its own repo, one folder per project, so code repos stay clean.
dev-core
Full development workflow — frame, shape, plan, implement, review, ship. Skills + agents (incl. /R-adversarial, /R-advisory), dual-harness task list + worktrees, safety hooks (Claude + Grok).
issue-triage
Triage/create GitHub issues — size/priority/lane/type labels, blocked-by deps, parent/child. Labels + native relations, no Projects V2.
repo-hygiene
Skills that keep a codebase healthy as agents work in it: repo orientation, docstring discipline, doc freshness, test coverage for new code, and pre-commit verification gates.