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.
npx skills add Comfy-Org/workflow_templates --skill managing-use-case-pagesgit clone --depth 1 https://github.com/Comfy-Org/workflow_templatesWrote 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/skills/comfy-org/workflow_templates/managing-use-case-pages)<a href="https://agentmods.dev/skills/comfy-org/workflow_templates/managing-use-case-pages"><img src="https://agentmods.dev/badge/skills/comfy-org/workflow_templates/managing-use-case-pages/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/skills/comfy-org/workflow_templates/managing-use-case-pages"><img src="https://agentmods.dev/badge/skills/comfy-org/workflow_templates/managing-use-case-pages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 107 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium Excessive Agency · line 153 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00140 | $0.03480 |
| Opus 5 | $0.00070 | $0.01740 |
| Sonnet 5 | $0.00028 | $0.00696 |
| Haiku 4.5 | $0.00014 | $0.00348 |
Grade A, and why
managing-use-case-pages scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s 'https://cloud.comfy.org/api/hub/workflows/index?status=approved' -o "$HUB_INDEX" How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Use-Case Pages
You are helping someone ship or update an SEO use-case landing page on the workflow site
(comfy.org/workflows/use-cases/<slug>/). The requester may be a content manager, a
growth person, or an engineer; they should never need to understand JSON, TypeScript, or
the build pipeline. You handle all of that. They contribute facts, judgment, and
approval.
The full rules live in site/docs/use-case-page-guide.md. This skill is the procedure; when it says "per the guide", follow that document.
How to interact with the requester
These rules apply to every step below, whether you run interactively (a person in the conversation) or non-interactively (triggered from a Slack thread or a PR comment):
- Decisions are theirs, mechanics are yours. Never invent a keyword, a clearance, or an app link. Never ask them to write JSON. Site-wide conventions (slug, title, h1 patterns) are presented for correction, not asked as questions; decisions and content require an explicit yes.
- If you cannot ask the requester directly (no interactive session), post your question where the request came from (the Slack thread or the PR) and stop until a named human answers. Do not proceed on assumptions.
- Silence is not approval. Every approval point below requires an explicit yes.
- Never merge a PR, never mark your own PR ready without the requester's go-ahead, and never push extra commits to an approved PR (pushing dismisses approvals; batch fixes into one push).
Entry point A: create a new page
Step 1: Collect the facts
Ask the requester for the keyword's row from the planning source named in the guide's "Where the Facts Come From" section (currently an internal keyword sheet; they paste the row or state the values). You need:
- the keyword (e.g. "ai logo generator")
- the gate value (brand-safety clearance)
- the published workflow / app links for it, if any
- search volume if available (goes in the PR body)
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.
- 9d ago First seen · 279 lines · 140 tokens per session scan A c5211f2e123a
managing-use-case-pages is a skill published in the GitHub repository Comfy-Org/workflow_templates (884 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 3,480 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…