菜单
How to use Forge to submit headless agent jobs, check status, and retrieve output via MCP tools. Use when the user wants to delegate work to a background agent, run a task on another LLM, or interact with forge.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Zate/cc-plugins --skill use命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create or update the project security baseline, profile, suppressions file, and gitignore entries for security scans
Fix or guide remediation for a specific security finding from the latest scan report
Run a security assessment using deterministic static analysis tools with LLM-powered triage
正在显示 SKILL.md
基于 SOC 职业分类
| name | use |
| description | How to use Forge to submit headless agent jobs, check status, and retrieve output via MCP tools. Use when the user wants to delegate work to a background agent, run a task on another LLM, or interact with forge. |
| user-invocable | true |
Forge runs tasks on LLM agents in the background via a daemon. Interact through MCP tools.
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 |
Check job status. Required: job_id (string).
Get completed job result. Required: job_id (string).
Returns: output content, metadata (agent, model, duration, tokens, cost).
List jobs. Optional: status filter (pending, running, completed, failed), limit (default 20).
1. forge_submit → returns job_id
2. forge_status → poll until "completed" or "failed"
3. forge_output → retrieve the result
pending → claimed → dispatched → running → validating → delivering → completed
Any state can transition to failed.
pending, check with forge_status or run /forge:setup.forge_list to monitor.["non-empty", "min-length:100"]).