latent-briefing

Compact orchestrator trajectories into worker KV caches using task-guided Attention Matching.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/ludotype/game-adventurertown --skill latent-briefing-ludotype
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: latent-briefing
Source: https://github.com/ludotype/game-adventurertown/tree/main/.agent/skills/latent-briefing
Command: npx skills add https://github.com/ludotype/game-adventurertown --skill latent-briefing-ludotype

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hierarchical multi-agent systems waste tokens by replaying the full orchestrator trajectory into every worker call, while summarization adds latency and loses information. This Skill explains how to transfer orchestrator state to workers at the representation level by compacting the worker model's KV cache instead of re-serializing context as text. ## Core Features & Use Cases - Task-guided KV compaction: Score trajectory positions by attention from the current worker task prompt, keeping only relevant tokens. - Shared global mask with MAD thresholding: Aggregate scores across layers and heads into one mask using a median + tau * MAD threshold for batched, low-latency compaction. - Decision framework: Compare Latent Briefing against prefix caching, summarization, and RAG to pick the right cross-agent memory mechanism. - Use Case: In a recursive orchestrator-worker system answering long-document questions, compact the growing orchestrator trajectory before each worker call to cut worker tokens while preserving task-relevant reasoning state. ## Quick Start Ask the assistant to explain how to share orchestrator memory with workers via KV cache compaction using Latent Briefing and Attention Matching.

Frequently Asked Questions about latent-briefing

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

FAQPage Schema
How do I share memory between agents without summarization?▼

Share memory at the representation level by compacting the orchestrator trajectory directly in the worker model's KV cache. Task-guided queries from the current worker prompt score which trajectory positions to keep, avoiding the latency and information loss of text summarization.

What is Attention Matching KV cache compaction?▼

Attention Matching seeks a smaller KV cache whose attention outputs approximate the full cache, using compacted keys, bias corrections, and reconstructed values. Latent Briefing adapts it with task-guided query vectors, a shared global mask across heads, and robust MAD-based thresholding.

Latent Briefing vs RAG vs summarization for multi-agent context?▼

Prefix caching suits stable repeated prefixes, summarization suits human-readable auditable state, and RAG suits sparse lookup over large corpora. Latent Briefing fits when workers need task-specific slices of orchestrator state and the runtime allows KV cache manipulation.

Can I use KV cache compaction with closed-model APIs?▼

No. Latent Briefing requires the inference runtime to inspect and rewrite worker KV state, which API-only stacks do not expose. It also assumes orchestrator and worker share the same model space, tokenizer, and attention layout.

Why does aggressive KV compaction hurt accuracy?▼

A high threshold tau drops more trajectory positions, and accuracy falls off a cliff once task-relevant evidence is removed. The optimal threshold is workload-dependent, so tune on validation data tracking accuracy, worker tokens, and compaction overhead together.