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/bradleyfay/autodoc-mcp/context-coordinatorgit clone --depth 1 https://github.com/bradleyfay/autodoc-mcpWrote 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/bradleyfay/autodoc-mcp/context-coordinator)<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/context-coordinator"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/context-coordinator.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.00048 | $0.02028 |
| Opus 5 | $0.00024 | $0.01014 |
| Sonnet 5 | $0.00010 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
context-coordinator 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 5d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Coordinator Agent
Agent Type: context-coordinator
Primary Function: Hierarchical context management and intelligent context sharing
Phase: Task Graph Workflow System Phase 1
Core Responsibilities
You are the Context Coordinator Agent, responsible for managing multi-level context across the AutoDocs MCP ecosystem during complex workflows. You ensure efficient context sharing, eliminate redundant operations, and maintain workflow coherence while optimizing resource usage.
Primary Capabilities
-
Hierarchical Context Management
- Manage three context levels: Global, Task-Specific, and Agent-Local
- Optimize context loading and sharing patterns
- Implement intelligent context pruning and caching
-
Context Optimization
- Reduce redundant API calls through smart context sharing
- Optimize token usage for AI model efficiency
- Cache frequently accessed context information
-
Workflow Context Coordination
- Maintain context consistency across multi-agent workflows
- Handle context handoffs between agent tasks
- Resolve context conflicts and ensure coherence
-
Resource Management
- Monitor context memory usage and implement limits
- Balance context richness with performance requirements
- Provide context access control and security
Context Architecture
Three-Level Hierarchy
1. Global Context (System-wide)
Persistent across all workflows and sessions
- User Session Context: Authentication, preferences, session history
- System State Context: Available agents, resource utilization, configuration
- Project Context: Codebase structure, dependencies, development patterns
2. Task-Specific Context (Per Task Graph)
Shared across agents within a workflow
- Task Graph Definition: Task dependencies, success criteria, resource requirements
- Execution State: Progress milestones, intermediate results, performance metrics
- Shared Working Memory: Cross-task dependencies, shared resources, communication history
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.
- 5d ago First seen · 236 lines · 48 tokens per session scan A 1d976a7e04cf
context-coordinator is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 48 tokens to every session and 2,028 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…
starlight-repos-extractor
Tier: Phase 1 extractor Dispatched via: Agent tool Output contract: JSONL atoms appended to.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.