Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/pr1m8/haive/multi_agent_state_guide_2025git clone --depth 1 https://github.com/pr1m8/haiveWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/pr1m8/haive/multi_agent_state_guide_2025)<a href="https://agentmods.dev/agents/pr1m8/haive/multi_agent_state_guide_2025"><img src="https://agentmods.dev/badge/agents/pr1m8/haive/multi_agent_state_guide_2025.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.02819 |
| Opus 5 | $0.00000 | $0.01409 |
| Sonnet 5 | $0.00000 | $0.00564 |
| Haiku 4.5 | $0.00000 | $0.00282 |
Grade A, and why
multi_agent_state_guide_2025 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MultiAgentState Guide - Haive Framework
Date: August 7, 2025
Version: 1.0
Purpose: Comprehensive guide to MultiAgentState schema and patterns
🎯 Overview
MultiAgentState is the core state container for multi-agent workflows in Haive. It provides:
- State isolation between agents without schema flattening
- Direct field updates for structured output agents
- Recompilation tracking for dynamic workflows
- Clean data flow between sequential agents
📋 Core Architecture
Class Definition
from haive.core.schema.prebuilt.multi_agent_state import MultiAgentState
from haive.core.schema.tool_state import ToolState
class MultiAgentState(ToolState):
"""Container state for multi-agent workflows."""
# Agent storage (list or dict)
agents: list[Any] | dict[str, Any]
# Isolated state for each agent
agent_states: dict[str, dict[str, Any]]
# Execution tracking
active_agent: str | None
agent_outputs: dict[str, Any] # Legacy message pattern
agent_execution_order: list[str]
# Recompilation management
agents_needing_recompile: set[str]
recompile_count: int
recompile_history: list[dict[str, Any]]
Key Insight: No Schema Flattening
Unlike previous approaches that tried to merge all agent schemas, MultiAgentState:
- Keeps each agent's schema independent
- Projects state to agents as needed
- Maintains type safety without complex merging
🏗️ State Management Patterns
1. Direct Field Updates (Recommended)
Agents with structured_output_model update container fields directly:
from pydantic import BaseModel
# Define structured outputs
class AnalysisResult(BaseModel):
score: float
findings: list[str]
class ReportResult(BaseModel):
summary: str
recommendations: list[str]
# Create agents with structured output
analyzer = SimpleAgentV3(
name="analyzer",
structured_output_model=AnalysisResult
)
reporter = SimpleAgentV3(
name="reporter",
structured_output_model=ReportResult
)
# Initialize state
state = MultiAgentState(agents=[analyzer, reporter])
# After analyzer runs, state has 'analyzer' field
# After reporter runs, state has 'reporter' field
# Both are typed and validated!
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 485 lines · 0 tokens per session scan A 5bb8b523b4fb
multi_agent_state_guide_2025 is an agent published in the GitHub repository pr1m8/haive (23 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,819 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
cr-custom-rules
Reviews a supplied diff against explicit repository rules from supplied rule sources. Use only when dispatched by the code-review skill with at least one rule source.
cr-security
Reviews a supplied diff for introduced, practically exploitable security vulnerabilities. Use only when dispatched by the code-review skill.
cr-structure
Reviews a supplied diff for introduced, concrete design and maintainability hazards. Use only when dispatched by the code-review skill.
cr-correctness
Reviews a supplied diff for introduced behavioral and contract defects. Use only when dispatched by the code-review skill.
cr-performance
Reviews a supplied diff for introduced, material performance regressions. Use only when dispatched by the code-review skill.
context-researcher
On-demand research agent that decomposes queries into multiple search angles, runs parallel memory lookups, and synthesizes a structured briefing. Use when deep memory context is needed for a topic, entity, or decision.