「opus」の検索結果

Answer a hard question by fanning it out to a PANEL of models running in parallel — each answering independently with web search and bash, none seeing the others' work — then having Opus 4.8 judge every response into a structured analysis (consensus, contradictions, partial coverage, unique insights, blind spots) and write a final answer grounded in it. The panel is two independent Opus 4.8 runs (slug opus4.8-4.8), Opus 4.8 + GPT-5.5 via codex (opus4.8-gpt5.5), Opus 4.8 + Gemini 3.1 Pro via agy (opus4.8-gemini3.1pro), or all three (opus4.8-gpt5.5-gemini3.1pro). Opus always judges and writes the final answer — the pipeline can't be reversed. Runs on local CLI subscriptions (no metered API), and saves a timestamped provenance .md per run. Use this whenever the user asks to "run it through Fusion", says /fusion, wants a multi-model / panel / ensemble answer, wants a question cross-checked across models, or wants a higher-confidence answer with consensus and blind spots surfaced — even if they don't say "fusion". General-purpose: any topic (research, law, strategy, technical, personal). Best for high-stakes research, design calls, and debugging where being confidently wrong is expensive.

日本語の概要は準備中です。原文の説明を表示しています。

Run fable-mode execution discipline on Claude Opus — the top of the escalation ladder. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on Opus ("fable on opus", "stage this on opus", "deep work mode, opus"). When a task exceeds Opus's ceiling, report that to the user rather than escalating further.

日本語の概要は準備中です。原文の説明を表示しています。

opus-reviewer(Opusモデル、read-only)にレビューさせ、各指摘を実コードで検証して修正/反証/受容/保留に仕分け、再レビューを反復する。未解決ゼロ・千日手・要ユーザー判断のいずれかで終了。Opusモデルでコードレビューを回したいときに使う。

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

Migre prompts e código de Claude Sonnet 4.0, Sonnet 4.5 ou Opus 4.1 para Opus 4.5. Use quando o usuário quiser atualizar sua base de código, prompts ou chamadas de API para usar Opus 4.5. Lida com atualizações de string de modelo e ajustes de prompt para diferenças comportamentais conhecidas de Opus 4.5. NÃO migra Haiku 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

Runs a multi-model orchestration workflow led by the session's Fable or Claude Opus model. Sends menial tool-calling work to Haiku subagents, judgment work to Opus subagents at an effort matched to each task, and high-stakes or fresh-perspective questions to a GPT-6 Astra Codex peer. Detects the lead from session context; `--lead fable` or `--lead opus` overrides. Use to orchestrate, delegate, fan out, get a decorrelated Codex opinion, run a blind Opus-Codex cross-check, or act as tech lead.

日本語の概要は準備中です。原文の説明を表示しています。

Direct and produce a short film made entirely in code, in one of the styles of the Lemo-Opuscar library (e.g. Impasto Oil Painting 油画厚涂, Watercolor Brush 水彩笔刷, Chinese Ink Wash 中国水墨, Ukiyo-e 浮世绘, Whiteboard Explainer 白板讲解). Use when the user asks for a video, film, short, promo, explainer or animation (视频、短片、动画、宣传片) in a named style; when they want a film made about their own topic and haven't chosen a style (help them choose); or when they ask which film styles there are. Not for editing or converting existing video files.

日本語の概要は準備中です。原文の説明を表示しています。

Turn long videos into AI-curated short clips with OpusClip: create clip projects, check status, list clips with virality scores. Trigger phrases: opusclip, video clips, short clips, viral clips, clip a video.

日本語の概要は準備中です。原文の説明を表示しています。

Run fable-mode execution discipline on Claude Fable 5.1 — the top of the escalation ladder and the strongest staged run available. Routes the task to the @fable-orchestrator agent with its model overridden to Fable (`model: "fable"`), which stages the work, delegates artifact production to @fable-worker-sonnet / @fable-worker-haiku, and cold-checks deliverables with @fable-verifier. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on the strongest model ("fable on fable", "stage this on fable", "deep work mode, fable", "run this on 5.1"), or when a fable-opus run reports the task exceeds Opus's ceiling. Benchmarked 2026-09-02: zero correctness delta on Fable 5.1 at ~1.1× tokens, ~2× wall — a provenance runner, not an accuracy runner. Do NOT use for ordinary single-pass tasks — prefer fable-opus, fable-sonnet, or fable-haiku when the task doesn't need peak reasoning. Fable is plan-included; bulk work still routes down-tier.

日本語の概要は準備中です。原文の説明を表示しています。

Automate Emailoctopus tasks via Rube MCP (Composio). Always search tools first for current schemas.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.

日本語の概要は準備中です。原文の説明を表示しています。

Configure Claude Octopus — redirects to /octo:setup interactive wizard

日本語の概要は準備中です。原文の説明を表示しています。

Thorough research across multiple sources — use for complex topics needing broad synthesis

日本語の概要は準備中です。原文の説明を表示しています。

OWASP compliance, vulnerability scanning, and adversarial red team testing — use for security reviews

日本語の概要は準備中です。原文の説明を表示しています。

Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests

日本語の概要は準備中です。原文の説明を表示しています。

Review system architecture, simplify boundaries, or compare interface designs from repository evidence

日本語の概要は準備中です。原文の説明を表示しています。

Design UI/UX systems with style guides, palettes, typography, and component specs for new interfaces

日本語の概要は準備中です。原文の説明を表示しています。

Design and build a 10-30 second motion-design showreel or brand reel in the style of Nate's Opus 5.5 "CLAUDE / MOTION REEL": one brand motif transformed through labeled craft chapters, a persistent HUD, cuts locked to a 120-130 BPM grid, a sub-second flurry, and a held logo lockup that answers the opening. Use when asked for a showreel, sizzle reel, brand reel, motion reel, "a reel like the Opus one", "show off motion design for <brand>", a 15-second brand film cut to music, or to study why a reference reel works and rebuild that energy for another brand.

日本語の概要は準備中です。原文の説明を表示しています。

Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the `omc-plan` skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in `.omc/plans/`, then DEEPENS that plan with a 3-round ITERATIVE fusion loop — each round an Opus 4.8 panelist (Agent subagent) and a GPT-5.5 panelist (via codex) critique/improve it IN PARALLEL and BLIND, then Opus 4.8 (the orchestrator) judges and synthesizes one tighter plan that seeds the next round, stopping early on convergence. Writes the final dense plan back to the same `.omc/plans/<slug>.md`, then offers the OMC handoff (`/omc-plan --review` → `/team` or `/ralph`). Use for high-stakes planning, architecture decisions, strategy calls, and hard debugging — especially when the user runs /plan or asks how to approach a non-trivial build. Reuses the `fusion` skill's run_codex.sh + judge rubric. NOT for trivial tasks (single pass is enough).

日本語の概要は準備中です。原文の説明を表示しています。

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

日本語の概要は準備中です。原文の説明を表示しています。