octocode-subagent

Orchestrates multi-agent delegation, model routing, and local Ollama token offload workflows.

921|75|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: octocode-subagent
Source: https://github.com/bgauryy/octocode-mcp/tree/main/skills/octocode-subagent
Command: npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Deciding when and how to delegate work to subagents is error-prone: spawning workers without clear ownership wastes tokens, merges conflict, and unverified worker output pollutes results. This Skill provides a host-agnostic operating model for task decomposition, specialist delegation, coordination, synthesis, and local Ollama offload so parallel work stays bounded and verifiable.

Core Features & Use Cases

  • Delegation gate and decomposition: Decides solo vs batch vs spawn, builds a dependency-aware DAG of worker tasks, and writes sealed packets with goal, scope, acceptance, and return shape.
  • Coordination and synthesis: Portable list/wait/steer/stop actions, barrier-before-synthesize merging, conflict-first resolution, and recovery escalation for stalled or failing workers.
  • Challenge techniques: Rubber-duck, interview, mimic-flow, red-team, blind review, and consensus patterns for challenging claims with fresh-context critics.
  • Local Ollama offload: GATE → ROUTE → RUN → VERIFY → REPORT loop for tool-less one-shot or map-reduce jobs (summarize, extract, classify, translate, vision) using live ollama list inventory and tier-based model selection.
  • Use Case: You have 40 large log files to classify. The skill gates the decision, routes to a small installed Ollama model, runs sealed packets per shard via scripts/ollama-worker.sh, verifies each return against a schema, and reports what was offloaded.

Quick Start

Ask the agent to break your large task into parallel workers with clear ownership, or to offload summarization of saved files to a local Ollama model after running the health check script.

Frequently Asked Questions about octocode-subagent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide when to spawn subagents instead of working solo?

Use the spawn gate: delegate only when it changes speed, expertise, isolation, or context quality, since the default is solo work. The skill's decompose reference builds a DAG of subtasks and tags each as sync-in-parent or async-spawn, capping fan-out at five by default.

How do I offload summarization to a local Ollama model?

Run scripts/ollama-health.sh to confirm the daemon, pick an exact model name from ollama list using the tier-based routing rules, then invoke scripts/ollama-worker.sh with --job, --input, and --out. Verify the return against the packet schema before integrating it.

Does this skill work with Claude Code, Cursor, or LangGraph?

Yes, it is host-agnostic and works with any spawn, Task, or teammate API including Cursor, Claude, Pi, OpenAI Agents, LangGraph, and A2A peers. Host-specific tool names are intentionally excluded; you map the portable coordinate actions to your local API.

Can local Ollama workers use tools or browse the web?

No, the local Ollama path is strictly tool-less one-shot or map-reduce work on text and images you already saved. Tool-using agent loops, MCP calls, and web fetching stay on the parent orchestrator or host subagents.

What happens when a worker stalls or returns conflicting results?

The recovery reference escalates through retry with tighter acceptance, replan, further decomposition, one model tier up, then stop-and-finish-in-parent. Before synthesizing, the parent waits on all live workers, merges conflicts first, and re-checks load-bearing anchors itself.

Why must worker packets be sealed with acceptance criteria?

Workers inherit no parent chat history, so the packet is their entire world: goal, context, scope, ownership, acceptance, and return shape. Empty or missing return shapes count as failed handbacks that must be re-asked or replanned.