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/kelp/agent-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/kelp/agent-plugins/next-issue)<a href="https://agentmods.dev/plugins/kelp/agent-plugins/next-issue"><img src="https://agentmods.dev/badge/plugins/kelp/agent-plugins/next-issue/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/kelp/agent-plugins/next-issue"><img src="https://agentmods.dev/badge/plugins/kelp/agent-plugins/next-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
next-issue 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": "next-issue",
"description": "Land one GitHub sub-issue as one pull request, or one parent issue's remaining sub-issues as a commit stack.",
"version": "0.4.2",
"author": {
"name": "Travis Cole"
},
"homepage": "https://github.com/kelp/agent-plugins",
"repository": "https://github.com/kelp/agent-plugins"
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 207 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 · 11 lines scan A a7e0d5cf16d6
next-issue is a plugin published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 1mo 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-09-07.
Other plugins, from other repositories
github-cli
GitHub CLI (gh) companion: security guard blocking write operations + comprehensive usage skill for automation, API access, and workflow patterns.
workspace-jj
Wave-based parallel orchestration with spec review gates for jj (Jujutsu) repositories.
todo
Filesystem-based task management with git integration - track tasks through open/wip/done lifecycle.
roadmap
Product management, roadmap analysis, and solution architecture with multi-agent orchestration.
spring-clean
Two passes over a repo. spring-clean measures against a declared scoreboard, deletes or gitignores what does not belong, relocates dev docs, notes, clones and dumps to a -workspace repo, splits oversized files, draws package boundaries and writes its plan to a numbered unit list that survives a dead context. w.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.