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/Malo-T/claude-toolbeltWrote 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/malo-t/claude-toolbelt/branch-recap)<a href="https://agentmods.dev/plugins/malo-t/claude-toolbelt/branch-recap"><img src="https://agentmods.dev/badge/plugins/malo-t/claude-toolbelt/branch-recap/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/malo-t/claude-toolbelt/branch-recap"><img src="https://agentmods.dev/badge/plugins/malo-t/claude-toolbelt/branch-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
branch-recap 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 9d 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
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "branch-recap",
"description": "Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.",
"version": "1.0.0",
"license": "MIT",
"author": {
"name": "Malo Toanen"
},
"homepage": "https://github.com/Malo-T/claude-toolbelt/tree/main/plugins/branch-recap"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 338 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.
- 9d ago First seen · 12 lines scan A b91994a9e159
branch-recap is a plugin published in the GitHub repository Malo-T/claude-toolbelt (2 stars, last pushed 19d 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
github
Skills for GitHub pull request workflows — creating PRs, addressing review feedback, and resolving threads.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
dootask
A DooTask plugin toolkit for creating plugins, preparing releases, improving project instructions, and making Conventional Commits. Conventional Commits are a standard format for describing Git changes.
sonu
Make your coding agent work like a senior teammate instead of an eager intern. /sonu:build writes every change in your style and test-first, then hands it back with the riskiest parts flagged before you review. /sonu:ship takes it from working tree to merged PR on its own — collecting every AI reviewer bot enabled on…
engineering-workflow-plugin
Skills for software engineering workflows: git operations, test fixing, code review, feature planning, and ensemble problem solving (generates multiple solutions in parallel and selects the best).
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…