A guide for using Forge, a background service that runs tasks through other AI agents and returns their results.

Use it to submit a task, choose an agent or model, attach input files, check progress, list jobs, and retrieve completed output.

It lets you delegate work without waiting in the current session and provides job status, output, model, duration, token, and cost details.

use — Skill for Claude Code by Zate/cc-plugins

Install

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.

Any agent

npx skills add Zate/cc-plugins --skill use

Clone the repo

git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Or install forge, the plugin that ships this one along with the rest of its 1 skill, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zate/cc-plugins/use/github.svg)](https://agentmods.dev/skills/zate/cc-plugins/use)

Your own site

<a href="https://agentmods.dev/skills/zate/cc-plugins/use"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/use/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zate/cc-plugins/use"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 638 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00049	$0.00638
Opus 5.5	$0.00020	$0.00255
Sonnet 5.5	$0.00010	$0.00128
Haiku 4.5	$0.00005	$0.00064

Measured 1mo ago against content hash 31290a235bfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/forge/skills/use/SKILL.md · 66 lines

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 with forge_status or run /forge:setup.
Jobs are async - submit returns immediately. Poll status or use forge_list to 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.

Read the full file on GitHub · 66 lines

Changes

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.

1mo ago First seen · 66 lines · 49 tokens per session scan A 31290a235bfa

Subscribe to this mod's changes

use is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 638 once invoked, about $0.0002 per session on Opus 5.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.

Building agents

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.