dbx-subagent-context-control

Control Codex subagent context inheritance and task scope with fork_context defaults.

5|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/DBvc/skills --skill dbx-subagent-context-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbx-subagent-context-control
Source: https://github.com/DBvc/skills/tree/main/skills/dbx-subagent-context-control
Command: npx skills add https://github.com/DBvc/skills --skill dbx-subagent-context-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex subagent delegation can easily leak context or cascade unwanted histories. This skill provides a structured, safe way to control subagent context inheritance, review delegation, and isolation to ensure predictable behavior.

Core Features & Use Cases

  • Context isolation: decide whether to inherit parent thread state when spawning subagents.
  • Explicit fork control: enforce fork_context=false by default and require fork_context=true only when explicitly requested.
  • Background planning and merging: generate 3-8 line background summaries and clear output contracts for subagents.
  • Safety and governance: guide subagent usage to avoid leakage of sensitive information and ensure proper merging of results.

Quick Start

Provide a minimal background, specify fork_context settings, and outline subagent spawn steps.

Frequently Asked Questions about dbx-subagent-context-control

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

FAQPage Schema
How do I control context inheritance when spawning Codex subagents?

Codex subagent context inheritance is controlled by setting fork_context to false by default and explicitly enabling true only when parent thread history must be inherited. This ensures safe delegation and predictable behavior.

What is the safest way to delegate review tasks to isolated subagents?

Isolated subagent review delegation requires specifying background summaries, output contracts, and clear termination conditions. This structured approach prevents unwanted history cascades and sensitive information leakage during parallel reviews.

Why does my subagent context leak parent thread history during parallel reviews?

Subagent context leaks during parallel reviews occur because fork_context defaults to true in uncontrolled delegations. Enforcing fork_context=false by default isolates the parent thread state and prevents unwanted history from cascading.

How do I generate background summaries and output contracts for subagent delegation?

Subagent delegation background summaries and output contracts are generated as 3-8 line structured descriptions. These guide subagent usage, define task scope, and ensure proper merging of isolated review results back to the parent.

Can I use explicit fork control for subagents requiring inherited parent state?

Explicit fork control allows subagents to inherit parent thread state by setting fork_context to true only when explicitly requested. This governance ensures history is shared solely when necessary, maintaining isolation by default.

When should I not use default context isolation for delegated reviewers?

Default context isolation for delegated reviewers should not be used when the subagent task explicitly requires inherited parent thread history. In these specific cases, setting fork_context=true overrides the safe default to enable state sharing.