본문으로 건너뛰기
cccskills
무료GitHub에 공개

mcsc

Delegate a task to another installed CLI harness (Antigravity/agy, OpenCode, Codex) from inside an AOS repo. Use this instead of shelling out to that CLI directly whenever one is installed — it wraps the wrapper flags for you and streams live tool-call telemetry to agenttrail, which is why the board updates in real time. Reach for it any time you're about to delegate work to another harness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

mcsc — Multi-CLI Subagent Configurator

mcsc (mcps/mcsc/) is AOS's own cross-harness delegation engine. It is the mandatory path for delegating work to another CLI harness inside an AOS-installed repo — not a Claude-Code-only convenience.

Why this exists

Three separate, harness-specific delegation paths already exist (the Claude Code plugins antigravity:delegate, opencode:opencode-rescue, codex:codex-rescue — see AGENTS.md's "Delegating to an external CLI"). Those are fine for interactive delegation from a Claude Code session, but they are Claude-Code-only, and none of them tell agenttrail's live board what is happening. mcsc's adapters (mcps/mcsc/packages/core/src/adapters/{agy,codex,opencode}.js) wrap each CLI once, work from any harness, and call emitTrail() around every delegated run — SessionStart/SessionEnd, plus live PreToolUse/PostToolUse where the underlying CLI supports structured/streaming output — so a delegated run shows up on the board the moment it starts, without any extra setup.

Skipping mcsc doesn't just lose convenience — it makes the delegated agent invisible to anyone watching the live map, and to anyone in this repo who asks "what are the other agents doing right now."

How to use it

Once installed (mcsc in mcp_config.json, entry point mcps/mcsc/server.js), it registers up to four MCP tools — one per installed CLI, only exposed when that CLI is detected as ready in the local inventory, and never offered back to a caller that's already running as that same CLI (MCSC_CALLER env var, avoids self-delegation loops):

  • delegate_agy — { prompt, model? } → Antigravity / Gemini. READ-ONLY until tested: use it for research, review and analysis, never for edits. The adapter can pass --mode accept-edits (write: true), but that path is untested and not part of the contract.
  • delegate_opencode — { prompt, model?, variant? } → OpenCode
  • delegate_codex — { prompt, model? } → Codex
  • delegate_smart — { task_type, prompt } → reads rulebook.yaml (or the bundled default) and picks the best CLI for that task type automatically

Call the tool that matches the harness you want, with a complete, self-contained prompt — the adapter underneath handles the CLI's actual flags, streams tool-call telemetry to agenttrail as it runs, and returns the final output. variant (OpenCode only) maps to --variant (reasoning effort).

Depth limit: one level, like a fork

Every adapter sets MCSC_DEPTH to the caller's depth plus one in the child's environment. An mcsc server that starts with MCSC_DEPTH >= 1 lists no tools and refuses every call. A delegated agent therefore cannot delegate again, so agy -> codex -> agy chains are impossible. MCSC_CALLER alone only excluded the caller's own CLI and was overwritten by each adapter.

What it is not

  • Not a replacement for the Claude Code delegation plugins for a quick, interactive, single-turn ask inside a Claude Code session — those remain fine for that case.
  • Not itself a review/QA step — verify a delegated result the same way AGENTS.md already says to: read the actual diff, never trust the returned status field alone.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hybridlabor-api/aos62026년 10월 16일 업데이트

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hybridlabor-api/aos62026년 10월 16일 업데이트

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hybridlabor-api/aos62026년 10월 16일 업데이트

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hybridlabor-api/aos62026년 10월 16일 업데이트

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hybridlabor-api/aos62026년 10월 16일 업데이트

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hybridlabor-api/aos62026년 10월 16일 업데이트

hybridlabor-api의 스킬 모두 보기

이 스킬의 문제 신고