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/zhebil/claude-code-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/zhebil/claude-code-plugins/auto-enrich)<a href="https://agentmods.dev/plugins/zhebil/claude-code-plugins/auto-enrich"><img src="https://agentmods.dev/badge/plugins/zhebil/claude-code-plugins/auto-enrich/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/zhebil/claude-code-plugins/auto-enrich"><img src="https://agentmods.dev/badge/plugins/zhebil/claude-code-plugins/auto-enrich.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
auto-enrich 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 3d 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": "auto-enrich",
"version": "1.4.1",
"description": "Auto-enrich user prompts with context for Jira tickets, GitHub PRs/issues/repos/files, GitLab issues/MRs/projects/files, and Sentry issues.",
"author": {
"name": "Zhebil"
},
"homepage": "https://github.com/zhebil/claude-code-plugins/tree/main/plugins/auto-enrich",
"repository": "https://github.com/zhebil/claude-code-plugins",
"license": "MIT",
"keywords": ["hooks", "jira", "github", "gitlab", "sentry", "context"]
}
What it installs
The manifest is a name and a version. 1 skill, 3 hooks travel with it, and installing the plugin installs all of them — 83 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.
- 3d ago Changed 9be742f20322
- 1mo ago First seen · 14 lines scan A 873a361ecdeb
auto-enrich is a plugin published in the GitHub repository zhebil/claude-code-plugins (7 stars, last pushed 3d 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
team-motivation
Team motivation and management skills including Daniel Pink's Autonomy, Mastery, Purpose (AMP) principles and Andy Grove's High Output Management (leverage, one-on-ones, OKRs, task-relevant maturity).
handbook-structured-plan-mode
Structured planning methodology for complex feature implementations through systematic task decomposition.
design-ops
Design operations toolkit for design companies - dashboard, integrations, and utility commands for team productivity.
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
fullstack-dev-kit
Issue-to-PR workflow for any tech stack: fetch stories from Jira/Linear/GitHub/Azure and Figma designs, plan-approval gate, adaptive quality + coverage gates, e2e generation, PR creation and review.
agent-dispatch
Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.