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/laurigates/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/laurigates/claude-plugins/comfyui-plugin)<a href="https://agentmods.dev/plugins/laurigates/claude-plugins/comfyui-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/comfyui-plugin/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/laurigates/claude-plugins/comfyui-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/comfyui-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
comfyui-plugin 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 2d 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": "comfyui-plugin",
"version": "1.14.2",
"description": "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",
"author": {
"name": "Lauri Gates"
},
"license": "MIT",
"keywords": [
"comfyui",
"custom-node",
"scaffold",
"litegraph",
"comfy-registry",
"gitops",
"screenshots",
"playwright"
]
}
What it installs
The manifest is a name and a version. 17 skills travel with it, and installing the plugin installs all of them — 857 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill comfy-node A 46 tokens
- Skill comfy-corpus-validation A 37 tokens
- Skill comfy-math-strings A 50 tokens
- Skill comfy-registry-lifecycle A 49 tokens
- Skill comfy-workflow-json A 52 tokens
- Skill comfy-workflow-layout A 43 tokens
- Skill comfyui-node-authoring A 52 tokens
- Skill comfyui-node-scaffold A 59 tokens
- Skill comfy-conditionals A 49 tokens
- Skill comfy-metadata A 54 tokens
- Skill comfy-subgraphs-app-mode A 55 tokens
- Skill comfyui-screenshot-pipeline A 47 tokens
- Skill comfy-flow-control A 47 tokens
- Skill comfy-image-utils A 63 tokens
- Skill comfy-debug-preview A 48 tokens
- Skill comfyui-pack-live-smoke B 48 tokens
- Skill comfy-cli B 58 tokens
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.
- 2d ago Changed 3eb0b0455fac
- 6d ago Changed 4224ffad393a
- 9d ago Changed caf9e73315c8
- 10d ago Changed 4e308005d31e
- 12d ago Changed ef2bc661527a
- 25d ago Changed · +4 lines 28756d47b284
- 1mo ago First seen · 17 lines scan A e1738242a2b6
comfyui-plugin is a plugin published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), 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
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
prflow
Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
contributor-writing
Writing skills for Shopware core contributors: Architecture Decision Records, PR descriptions (trunk and feature-branch formats), commit messages, and RELEASEINFO/UPGRADE entries. Analyzes branch diffs, classifies changes, and writes content calibrated to change magnitude.
release-conductor
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.
playbooks-virtuoso
5 playbook skills — PHP upgrade, Composer dependencies, branch finishing, ticket delivery, and worktree ops.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.