latent-briefing

Share relevant orchestrator reasoning state between agents to reduce token costs.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/Kushal9889/claude-plugins --skill latent-briefing-kushal9889
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: latent-briefing
Source: https://github.com/Kushal9889/claude-plugins/tree/main/context-engineering/skills/latent-briefing
Command: npx skills add https://github.com/Kushal9889/claude-plugins --skill latent-briefing-kushal9889

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill addresses the problem of hierarchical multi-agent systems paying for the same context twice, leading to high token costs and inefficiencies.

Core Features & Use Cases

  • Representation-Level Memory Sharing: Shares memory at the representation level, rather than the text level, for efficient multi-agent handoff.
  • Task-Guided Queries: Uses task-guided query vectors to determine which parts of the orchestrator's trajectory are relevant to the current worker task.
  • Shared Global Mask: Aggregates scores across layers and heads into one per-position score for batched operations.
  • Robust Thresholding: Uses a robust thresholding method to determine which positions in the trajectory to keep.
  • Use Case: Ideal for orchestrator-worker or supervisor-specialist systems where workers need access to prior orchestrator state without replaying the full trajectory as text.

Quick Start

Activate the latent-briefing skill when needed to share memory between agents in a multi-agent system.

Frequently Asked Questions about latent-briefing

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

FAQPage Schema
How do I reduce token costs when sharing context between agents in a multi-agent system?

To reduce token costs in a multi-agent system, share relevant parts of the orchestrator's reasoning state at the representation level instead of replaying the full trajectory as text. This prevents paying for the same context twice during worker handoffs.

How does representation-level memory sharing work for hierarchical multi-agent inference?

Representation-level memory sharing works by using task-guided query vectors to determine which parts of the orchestrator's trajectory are relevant to the worker task. It aggregates scores across layers and heads into one per-position score for batched operations.

When do I need task-specific memory sharing in orchestrator-worker systems?

You need task-specific memory sharing in orchestrator-worker systems when workers require access to prior orchestrator state without incurring high token costs from replaying the full historical trajectory as text.

How do I determine which positions in an orchestrator's trajectory to keep for a worker task?

You determine which trajectory positions to keep by applying a robust thresholding method to the aggregated per-position scores, filtering the orchestrator's reasoning state to share only the most relevant context for the specific worker task.

Does this memory sharing approach work with supervisor-specialist systems?

Yes, this memory sharing approach works with supervisor-specialist systems. It is optimized for hierarchical systems where specialists need access to prior supervisor state without replaying the full trajectory as text.

What are the limitations of using shared global masks for multi-agent inference optimization?

A limitation of using shared global masks for multi-agent inference optimization is that it aggregates scores across all layers and heads into a single per-position score, which may oversimplify complex attention patterns required by highly specialized worker tasks.