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 osouthgate/agent-plus --skill diff-summarygit clone --depth 1 https://github.com/osouthgate/agent-plusWrote 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/osouthgate/agent-plus/diff-summary)<a href="https://agentmods.dev/skills/osouthgate/agent-plus/diff-summary"><img src="https://agentmods.dev/badge/skills/osouthgate/agent-plus/diff-summary/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/osouthgate/agent-plus/diff-summary"><img src="https://agentmods.dev/badge/skills/osouthgate/agent-plus/diff-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00109 | $0.01391 |
| Opus 5.5 | $0.00044 | $0.00556 |
| Sonnet 5.5 | $0.00022 | $0.00278 |
| Haiku 4.5 | $0.00011 | $0.00139 |
Grade A, and why
diff-summary 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
diff-summary
Structured triage of a git diff. One call replaces the per-file Read sweep an agent normally does to figure out which files in a diff are tests, which touch the public API, which are migrations, which need careful review.
Lives at ${CLAUDE_SKILL_DIR}/../../bin/diff-summary; the plugin auto-adds bin/ to PATH, so just run diff-summary ....
When to reach for this
- User asks "what changed in this branch / triage this PR / is this safe to merge" → run
diff-summary --base main --pretty. Read thesummary.highRiskFilesandsummary.byRolefirst; only Read individual files where risk is HIGH. - User asks "what am I about to commit" → run
diff-summary --pretty(default = working tree) ordiff-summary --staged --prettyafter agit add. - Pre-PR sanity check →
diff-summary --base main --risk medium --prettyshows only the files that need a second look. - "Did I forget to update the tests?" → check
summary.sourceFilesWithoutTestChanges.
Headline command
diff-summary # working tree (default)
diff-summary --staged # staged index
diff-summary --base main # <base>...HEAD (3-dot merge-base)
diff-summary --range A..B # explicit range, passed verbatim
diff-summary --max-files 200 # cap files[] (default 200)
diff-summary --include-patches # include raw unified diff per file (opt-in)
diff-summary --public-api-only # filter files[] to publicApiTouched only
diff-summary --risk medium # filter files[] to risk >= MIN
diff-summary --output /tmp/d.json --shape-depth 2 # offload large payload
diff-summary --pretty # indented JSON
The four diff-source flags (--staged, --base, --range, default) are mutually exclusive.
Output shape (truncated)
{
"tool": {"name": "diff-summary", "version": "0.2.1"},
"mode": "base",
"base": "main",
"head": "abc1234",
"branch": "feature/foo",
"summarizedAt": "2026-04-28T12:34:56Z",
"stats": {"files": 12, "insertions": 234, "deletions": 67, "movedLinesEstimate": 18},
"files": [
{
"path": "src/foo.ts",
"status": "modified",
"role": "source",
"language": "typescript",
"insertions": 42, "deletions": 5,
"binary": false,
"publicApiTouched": true,
"risk": "high",
"riskReasons": ["touches-public-api", "no-test-changes"]
}
],
"summary": {
"byRole": {"source": 5, "test": 3, "config": 2, "doc": 1, "generated": 1},
"highRiskFiles": ["src/foo.ts"],
"testFilesTouched": 3,
"sourceFilesWithoutTestChanges": ["src/bar.ts"],
"publicApiTouches": ["src/foo.ts"],
"migrationsTouched": [],
"secretsRiskFiles": []
}
}
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 · 90 lines · 109 tokens per session scan A e76840e23df7
diff-summary is a skill published in the GitHub repository osouthgate/agent-plus (4 stars, last pushed 3mo ago), licensed MIT. It adds 109 tokens to every session and 1,391 once invoked, about $0.0004 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-31.
Other skills, from other repositories
loop-gh-pr
A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.
loop-bb-pr
A command that prepares a repeating check for a Bitbucket pull request. A pull request is a request to review and merge code changes into a project.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.
session-boundary
Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.
apply-fixes
Internal skill for commands. Apply a review's verified fixes to the working tree when nothing needs deciding - the --fix flag of /lets:check, /lets:review and /lets:handoff. Do not trigger on user conversation - only when one of those commands runs with --fix.
fix
Read this repo's open issues, triage them, and open one pull request per issue that can be fixed without a judgement call. Issues that need a decision, or that look stale or superseded, are reported with a recommendation rather than guessed at.