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/ncaq/konokaWrote 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/ncaq/konoka/misuzu)<a href="https://agentmods.dev/plugins/ncaq/konoka/misuzu"><img src="https://agentmods.dev/badge/plugins/ncaq/konoka/misuzu/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/ncaq/konoka/misuzu"><img src="https://agentmods.dev/badge/plugins/ncaq/konoka/misuzu.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
misuzu 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "misuzu",
"version": "2.0.2",
"description": "Respond to PR review comments semi-automatically. Splits review findings into logical units, fixes and commits them one by one, then replies and resolves review threads.",
"dependencies": ["commit"],
"author": {
"name": "ncaq",
"email": "[email protected]",
"url": "https://github.com/ncaq"
},
"homepage": "https://github.com/ncaq/konoka/tree/master/plugins/misuzu",
"repository": "https://github.com/ncaq/konoka",
"license": "Apache-2.0",
"keywords": ["github", "pull-request", "resolve", "respond", "review"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 59 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 · 17 lines scan A 589b2f7cdf7f
misuzu is a plugin published in the GitHub repository ncaq/konoka (3 stars, last pushed yesterday), 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. 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.
manifest-dev-tools
Tools for prompts and PRs alongside the manifest workflow. Includes collaborative PR walkthroughs, autonomous PR review that independently re-verifies a manifest gate by gate, author-side PR babysitting that drives the lifecycle toward green and mergeable, gap-calibrated prompt engineering, standalone goals distilled…
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
pull-request
Pull request workflows: create, update, babysit CI, and reviewer follow-up.
coding
Opinionated Claude Code workflow skills: clear and unambiguous technical writing (write-clearly), iterative planning (replan), proof-based code review (review, review-staged, second-opinion), disciplined Conventional-Commit staging (gitplan, stage), finding the session that wrote an uncommitted change (find), and the…