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 agentmods add skills/zate/cc-plugins/usenpx skills add Zate/cc-plugins --skill usegit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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 | $0.00049 | $0.00638 |
| Opus 5 | $0.00024 | $0.00319 |
| Sonnet 5 | $0.00010 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
use 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge: Headless Agent Job Runner
Forge runs tasks on LLM agents in the background via a daemon. Interact through MCP tools.
MCP Tools
forge_submit
Submit a job. Returns a job ID.
Required: task (string) - the prompt/task description.
Optional:
| Parameter | Type | Description |
|---|---|---|
agent |
string | claude (default), gemini, local, lmstudio |
model |
string | Agent-specific: sonnet, haiku, opus, gemini-2.5-pro, etc. |
timeout |
string | Duration: 30s, 10m (default), 1h |
input_files |
string[] | File paths to include as context |
output_format |
string | markdown (default), json, yaml, code, raw |
constraints |
string[] | Output validation constraints |
tags |
string[] | Tags for filtering/organization |
forge_status
Check job status. Required: job_id (string).
forge_output
Get completed job result. Required: job_id (string).
Returns: output content, metadata (agent, model, duration, tokens, cost).
forge_list
List jobs. Optional: status filter (pending, running, completed, failed), limit (default 20).
Workflow
1. forge_submit → returns job_id
2. forge_status → poll until "completed" or "failed"
3. forge_output → retrieve the result
Job States
pending → claimed → dispatched → running → validating → delivering → completed
Any state can transition to failed.
Tips
- Daemon must be running for jobs to process. If jobs stay
pending, check withforge_statusor run/forge:setup. - Jobs are async - submit returns immediately. Poll status or use
forge_listto monitor. - Claude agent uses Claude CLI with full tool use (file editing, bash). Other agents are completion-only.
- Input files let you pass context files to the job agent.
- Constraints validate output (e.g.,
["non-empty", "min-length:100"]).
When NOT to Use
- For tasks that should happen in the current session (just do them directly).
- When you need interactive back-and-forth with the user during the task.
- Forge is for fire-and-forget background work.
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 First seen · 66 lines · 49 tokens per session scan A 31290a235bfa
use is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 638 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…