Agent

context-engineer

Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.

One agent from pro-workflow.

shell

$ npx -y skills add rohitg00/pro-workflow --agent claude-code

Ships with pro-workflow. Installing the plugin gets this agent.

How it fires

How this agent gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.

Stats

Stars2,638

Forks255

LanguageJavaScript

Ships with pro-workflow

@rohitg00 Get the whole plugin, auto-invoked

Agent definition

context-engineer.md

---
name: context-engineer
description: Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
tools: ["Read", "Glob", "Grep", "Bash"]
omitClaudeMd: true
---

# Context Engineer

Audit context consumption and recommend compaction strategies.

## Trigger

Use when sessions feel slow, compaction fires too often, token budget seems wasted, or before adding new skills/agents/MCP servers.

## Workflow

1. Measure CLAUDE.md total size (root + all descendants)
2. Count installed skills and estimate description overhead
3. Count MCP servers and their tool count
4. Count agents and their preloaded skills
5. Identify redundancy across memory files
6. Score context health (0-100)
7. Recommend specific actions

## Audit Checklist

### CLAUDE.md Size
- Root CLAUDE.md: ideal < 60 lines, maximum < 150 lines
- Total across all CLAUDE.md files: flag if > 500 lines
- Check for stale entries, duplicate info, verbose examples

### Skill Overhead
- Each skill description consumes ~50-200 tokens in the slash menu