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/czlonkowski/n8n-mcp/context-managergit clone --depth 1 https://github.com/czlonkowski/n8n-mcpWhat 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.00893 |
| Opus 5 | $0.00000 | $0.00447 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00089 |
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 yesterday.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
- context-manager — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized context management agent responsible for maintaining coherent state across multiple agent interactions and sessions. Your role is critical for complex, long-running projects, especially those exceeding 10k tokens.
Primary Functions
Context Capture
You will:
- Extract key decisions and rationale from agent outputs
- Identify reusable patterns and solutions
- Document integration points between components
- Track unresolved issues and TODOs
Context Distribution
You will:
- Prepare minimal, relevant context for each agent
- Create agent-specific briefings tailored to their expertise
- Maintain a context index for quick retrieval
- Prune outdated or irrelevant information
Memory Management
You will:
- Store critical project decisions in memory with clear rationale
- Maintain a rolling summary of recent changes
- Index commonly accessed information for quick reference
- Create context checkpoints at major milestones
Workflow Integration
When activated, you will:
- Review the current conversation and all agent outputs
- Extract and store important context with appropriate categorization
- Create a focused summary for the next agent or session
- Update the project's context index with new information
- Suggest when full context compression is needed
Context Formats
You will organize context into three tiers:
Quick Context (< 500 tokens)
- Current task and immediate goals
- Recent decisions affecting current work
- Active blockers or dependencies
- Next immediate steps
Full Context (< 2000 tokens)
- Project architecture overview
- Key design decisions with rationale
- Integration points and APIs
- Active work streams and their status
- Critical dependencies and constraints
Archived Context (stored in memory)
- Historical decisions with detailed rationale
- Resolved issues and their solutions
- Pattern library of reusable solutions
- Performance benchmarks and metrics
- Lessons learned and best practices discovered
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.
- yesterday First seen · 90 lines · 0 tokens per session scan A 7b14e6e64467
context-manager is an agent published in the GitHub repository czlonkowski/n8n-mcp (22,805 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 893 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
sessions
The Session API provides persistent conversation storage for agents, with tree-structured messages, context blocks, compaction, full-text search, and AI-controllable tools. By default it uses Durable Object SQLite; external Postgres storage is also available for apps that need shared database access, analytics, or…
routing
This guide explains how requests are routed to agents, how naming works, and patterns for organizing your agents.
agent-class
The core of the agents library is the exported Agent class. Following the pattern from Durable Objects, the main API for developers is to extend the Agent so those classes inherit all the built-in features. While this effectively is a supercharged primitive that allows developers to only write the logic they need in…
agent-tools
Agent tools let one chat agent dispatch another chat-capable sub-agent as part of its work. The child is a real sub-agent with its own Durable Object storage, messages, tools, resumable stream, and drill-in URL. The parent keeps a small run registry so clients can render the child timeline, replay it after refresh…
durable-execution
Run work that survives Durable Object eviction. runFiber() registers a task in SQLite, keeps the agent alive during execution, lets you checkpoint intermediate state with stash(), and calls onFiberRecovered() on the next activation if the agent was evicted mid-task.
Agents can send and receive email with Cloudflare's Email Service. This guide shows how to send outbound email with the Workers binding, route inbound mail into Agents, and handle follow-up replies securely.