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 laurigates/claude-pluginsnpx agentmods add plugins/laurigates/claude-plugins/comfyui-plugingit 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.svg" alt="Measured on agentmods" 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 today.
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.13.7",
"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",
"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-registry-lifecycle A 49 tokens
- Skill comfy-image-utils A 63 tokens
- Skill comfy-math-strings A 50 tokens
- Skill comfy-node A 46 tokens
- Skill comfyui-node-authoring A 52 tokens
- Skill comfy-conditionals A 49 tokens
- Skill comfy-debug-preview A 48 tokens
- Skill comfy-flow-control A 47 tokens
- Skill comfy-corpus-validation A 37 tokens
- Skill comfy-metadata A 54 tokens
- Skill comfy-workflow-json A 52 tokens
- Skill comfy-workflow-layout A 43 tokens
- Skill comfyui-node-scaffold A 59 tokens
- Skill comfy-subgraphs-app-mode A 55 tokens
- Skill comfyui-screenshot-pipeline A 47 tokens
- Skill comfyui-pack-live-smoke B 48 tokens
- Skill comfy-cli D 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.
- today First seen · 17 lines scan A e1738242a2b6
comfyui-plugin is a plugin published in the GitHub repository laurigates/claude-plugins (57 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: commit, pull-request, release-tag, issue-create.
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.
instruction-placement
Routes agent-instruction content to the surface that loads it at the right moment. The audit skill sweeps a repository's instruction layer and its ordinary markdown for content whose scope is narrower than the surface carrying it — conventions keyed to one file type or one subtree sitting in an always-loaded CLAUDE.md.