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.
/plugin marketplace add juanmhidalgo/claude-pluginsnpx agentmods add plugins/juanmhidalgo/claude-plugins/github-issuesgit clone --depth 1 https://github.com/juanmhidalgo/claude-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/juanmhidalgo/claude-plugins/github-issues)<a href="https://agentmods.dev/plugins/juanmhidalgo/claude-plugins/github-issues"><img src="https://agentmods.dev/badge/plugins/juanmhidalgo/claude-plugins/github-issues.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
github-issues 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 yesterday.
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": "github-issues",
"description": "Fix GitHub Issues: fetch issue details, explore the codebase, plan and implement the fix, with multi-repo handoff support",
"version": "1.2.2",
"author": {
"name": "Juan M. Hidalgo"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 41 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.
- yesterday First seen · 9 lines scan A a0a6d4557052
github-issues is a plugin published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d 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-03.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills-only: owns folder layout and templates; runs the Obsidian CLI directly via the official obsidian-cli skill.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.