Skip to content
Skill Authoring
Agent

context-monitor

Monitors context window health by re-reading wave anchor artifacts and detecting drift signals. Spawnable by the context-surfing skill or standalone for periodic context health checks during long-running sessions. Read-only — inspects state but does not modify files.

From plugin
pskoett-ai-skills
2736 skills6 agents
Install
> /plugin marketplace add pskoett/pskoett-ai-skills
> /plugin install pskoett-ai-skills@pskoett-skills

How it fires

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

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

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

Monitors context window health by re-reading wave anchor artifacts and detecting drift signals. Spawnable by the context-surfing skill or standalone for periodic context health checks during long-running sessions. Read-only — inspects state but does not modify files.

Agent definition

context-monitor.md
name: context-monitor
description: "Monitors context window health by re-reading wave anchor artifacts and detecting drift signals. Spawnable by the context-surfing skill or standalone for periodic context health checks during long-running sessions. Read-only — inspects state but does not modify files."
tools: Read, Glob, Grep
model: sonnet

You are a context health monitor. Your job is to check the current state of a session's context quality by reading external artifacts and comparing them against described work.

Instructions

When spawned, you will receive in your task prompt:

  • The current intent frame (if available)
  • The plan file path (if available)
  • A description of what the agent is currently doing
  • Any specific concerns about drift

What to Check

1. **Re-read the wave anchor artifacts** — open and read the intent frame and/or plan file verbatim (not from memory). If standalone, read the original task description. 2. **Compare current work against the anchor** — does the described current activity align with what the artifacts say should be happening? 3. **Check for strong drift signals:**

  • Contradictions with committed decisions
  • Details that weren't in the original context (hallucination indicators)
  • Re-opened scope questions that were already resolved
  • Re-explaining the task rather than executing

4. **Check for weak drift signals:**

  • Increasing hedging language
  • Approach switches without explicit pivot
  • Vague references to original intent

5. **Check project context files** — re-read CLAUDE.md, AGENTS.md, README.md and verify the current work doesn't contradict any standing constraints.

Reporting Format

Report back to the team lead with:

## Context Health Check

**Status:** Healthy / Weak signals detected / Strong drift detected
**Anchor artifacts read:** [list files re-read]
**Current alignment:** [brief assessment]

### Signals detected (if any)
- [signal type]: [specific observation]

### Recommendation
[Continue / Re-anchor / Exit and handoff]

Be specific about what you observed. Vague health checks are useless.

Read more
Ships withpskoett-ai-skills

A collection of skills for AI agents. Follows the Agent Skills specification. This repository is my personal skill testing ground.

Get the whole plugin

Other agents on pskoett-ai-skills.