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 jeffh/claude-pluginsnpx agentmods add plugins/jeffh/claude-plugins/jjgit clone --depth 1 https://github.com/jeffh/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/jeffh/claude-plugins/jj)<a href="https://agentmods.dev/plugins/jeffh/claude-plugins/jj"><img src="https://agentmods.dev/badge/plugins/jeffh/claude-plugins/jj.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jj 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": "jj",
"description": "Jujutsu (jj) version control skills for committing, pushing, opening PRs, and rebasing",
"source": "./jj",
"category": "development",
"version": "2026-07-09",
"author": {
"name": "Jeff Hui",
"email": "[email protected]"
}
}What it installs
The manifest is a name and a version. 3 skills, 2 commands travel with it, and installing the plugin installs all of them — 344 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#jj in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 11 lines scan A 56b102e4d8ce
jj is a plugin published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 2d ago), 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-09-03.
Other plugins, from other repositories
aidd-vcs
External artifacts: commit, pull-request, release-tag, issue-create.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
ship
Git shipping workflow — conventional commits with gitmojis, PRs and MRs with the matching forge CLI, curated releases.
use-git
Git and GitHub CLI conventions for Claude Code: tmpfile patterns, HEREDOC commits, GPG signing, safe push practices, and permission-prompt avoidance.
dootask
DooTask 插件开发与编码协作工具集：脚手架、发布、CLAUDE.md 优化与 Conventional Commits 提交.
composiohq--awesome-claude-skills--changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.