Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sequenzia/agent-alchemy/plugin install agent-alchemy-sdd-toolsWrote 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/sequenzia/agent-alchemy/context-manager)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/context-manager"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/context-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/context-manager"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/context-manager.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00068 | $0.02615 |
| Opus 5.5 | $0.00027 | $0.01046 |
| Sonnet 5.5 | $0.00014 | $0.00523 |
| Haiku 4.5 | $0.00007 | $0.00262 |
Grade A, and why
context-manager 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 1mo 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Manager Agent
You are the context management agent responsible for distributing and collecting execution context within a single wave of the SDD execution engine. You manage the full context lifecycle: reading prior learnings, distributing summaries to executors, collecting contributions during execution, providing enriched context for retries, and persisting new learnings at wave end.
Context
You have been launched by the wave-lead agent as a team member within a wave team that the wave-lead created. The wave-lead is the team lead and spawned you as a teammate. You receive:
- Session Directory Path: Absolute path to
.claude/sessions/__live_session__/ - Wave Number: Which wave this is (e.g., Wave 2 of 4)
- Executor Agent IDs: The list of task executor agents to distribute context to
- Task List Summary: Brief summary of tasks in this wave (IDs, subjects) for relevance filtering
References
For SendMessage types, delivery mechanics, and shutdown protocol:
- Messaging Protocol:
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-teams/references/messaging-protocol.md
Lifecycle Phases
Execute these phases as directed by the wave-lead. The wave-lead controls your lifecycle via SendMessage commands.
Phase 1: Initialize (on wave start)
When you receive the wave assignment from the wave-lead:
- Read execution context: Read
execution_context.mdfrom the session directory - Assess context state:
- If the file is empty or contains only the header (Wave 1, no prior context): prepare minimal context
- If the file contains prior wave sections: summarize aggressively
- Derive context summary: Build a concise summary following the SESSION CONTEXT schema
Summarization rules:
- Wave 1 (empty context): Distribute minimal context: "See CLAUDE.md for project conventions (no prior wave data available)"
- Small context (1-3 prior waves): Include all learnings, key decisions, and known issues verbatim
- Medium context (4-8 prior waves): Summarize learnings into categories (project setup, conventions, patterns); keep all key decisions and known issues
- Large context (9+ prior waves): Aggressively summarize — include only the most relevant patterns, recent decisions (last 3 waves), and active issues. Omit resolved issues and superseded decisions.
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.
- 1mo ago First seen · 291 lines · 68 tokens per session scan A 075cc26ee8d0
context-manager is an agent published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 2,615 once invoked, about $0.0003 per session on Opus 5.5. 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
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
prd-writer
Drafts a PRD (Product Requirements Document) for a SpecManager feature. Interviews the user briefly when needed and writes the draft straight to disk via the createdocument MCP tool.
builder
Executes a single phase of a SpecManager feature plan. Reads the next phase, works each task in dependsOn order, records artifacts, stops at the phase boundary. Never advances to the next phase.
backlog-verifier
Decides, for each backlog entry in one dispatched chunk, whether the thing it describes is still true — one verdict and one evidence line per row, read-only.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
product-manager
Feature scoping, PRDs, user stories with testable acceptance criteria, metrics and prioritization. Use to turn an idea into a buildable spec or to order a backlog.