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/pr)<a href="https://agentmods.dev/plugins/ncaq/konoka/pr"><img src="https://agentmods.dev/badge/plugins/ncaq/konoka/pr/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/pr"><img src="https://agentmods.dev/badge/plugins/ncaq/konoka/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pr 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": "pr",
"version": "1.4.0",
"description": "Create a GitHub pull request from the current branch.",
"dependencies": ["commit"],
"author": {
"name": "ncaq",
"email": "[email protected]",
"url": "https://github.com/ncaq"
},
"homepage": "https://github.com/ncaq/konoka/tree/master/plugins/pr",
"repository": "https://github.com/ncaq/konoka",
"license": "Apache-2.0",
"keywords": ["pull-request", "github", "git"]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 90 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 e904b829f1dc
pr 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
agent-based-development
Full async multi-agent development workflow: Planning → Design → Dev → Security/Tech Review loop with file-based handoffs and release-branch Git model.
changelog-generator
Generates a structured CHANGELOG.md following Keep a Changelog format from git history and ABD handoff artifacts. Prepends new version sections to existing changelogs.
git-workflow
Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.
pre-commit
Fast pre-commit quality gate: secrets, dead code, naming, conflict markers, and direct-to-main protection. Installs as a git hook.
agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows. Plus two opt-in hooks: leg-guard…
claim-check
Verifies test-count claims against what your suite actually did, before a commit lands. Supports pytest, vitest and jest. If the message makes no claim, it does nothing.