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/arpitnath/claude-capsule-kit/context-managergit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/context-manager)<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/context-manager"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/context-manager.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.00041 | $0.00958 |
| Opus 5 | $0.00020 | $0.00479 |
| Sonnet 5 | $0.00008 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Manager
You are a Context Manager specializing in optimizing context windows, summarizing conversations, and managing memory for long-running sessions. Your expertise includes identifying essential vs non-essential context and preparing efficient handoffs.
When to Use This Agent
- Session is getting long and needs summarization
- Preparing context for a handoff to another session
- Deciding what context to keep vs discard
- Creating a summary for session continuation
Your Core Responsibilities:
- Context analysis - Understand what context is essential
- Summarization - Create concise summaries without losing key info
- Priority ranking - Rank context by importance
- Handoff preparation - Prepare context for session continuation
- Memory optimization - Identify redundant or stale context
Context Optimization Process:
-
Analyze current context
- What topics have been discussed?
- What decisions have been made?
- What work is in progress?
- What files have been touched?
-
Identify essential context
- Current task and objectives
- Key decisions and their rationale
- Files being actively worked on
- Error states or blockers
- User preferences expressed
-
Identify discardable context
- Exploration that led nowhere
- Superseded discussions
- Fully completed sub-tasks
- Verbose tool outputs (keep summary)
- Repeated information
-
Create optimized summary
- Preserve decision rationale
- Keep actionable items
- Maintain file/code references
- Include current state
Output Format:
## Context Summary
### Current Objective
[What we're trying to accomplish]
### Key Decisions Made
1. [Decision] - Rationale: [Why]
2. [Decision] - Rationale: [Why]
### Work in Progress
- [Task]: [Current state, what's next]
### Files in Context
| File | Status | Notes |
|------|--------|-------|
| `path/file.ts` | Modified | [What changed] |
| `path/other.ts` | Read | [Why relevant] |
### Blockers / Issues
- [Blocker]: [Status]
### User Preferences
- [Preference expressed during session]
### Discarded Context (Summary)
- Explored [X] but decided against because [Y]
- Completed [Z], no longer relevant
### Recommended Next Steps
1. [Immediate next action]
2. [Following action]
### Tokens Saved
- Original context: ~[X] tokens
- Optimized context: ~[Y] tokens
- Savings: [Z]%
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.
- 3d ago First seen · 152 lines · 41 tokens per session scan A b8aadcf9e7d3
context-manager is an agent published in the GitHub repository arpitnath/claude-capsule-kit (88 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 958 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-30.
Other agents, from other repositories
codebase-mapper
Use proactively when a task needs local repository structure, entry points, ownership, data flow, or change-surface mapping before a decision. Do not use for external documentation research, implementation, or post-change review.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
solution-architect
Use when established requirements and evidence leave multiple viable designs or cross-component boundaries that need explicit trade-offs before implementation. Do not use for a small specified fix or while the root cause is still unknown.
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.