context-engineer v1.1.2 active
by Silvester Divas
Claude Code Plugin

Context engineering, shipped.

One plugin. 9 techniques. Zero wasted tokens.

Install Now See What's Inside Read the Guide
bash scorecard.sh
┌────────────────────────────────────────────────────────────┐
│ context-engineer v1.1.2 · Health Scorecard │
└────────────────────────────────────────────────────────────┘
 
● CLAUDE.md Budget ✓ Fresh context ✓ Tools ✓
● Token-Saving Hooks test ✓ build ✓ lint ✓
○ Fresh Context No active handoff files
● Git Hygiene Clean working tree
● Project Structure All files < 500 lines
 
┌────────────────────────────────────────────────────────────┐
│ Score: 4/4 passing · Your context is engineered. │
└────────────────────────────────────────────────────────────┘
 
Token Savings
test ████████████████░░░░ ~80%
build ██████████████████░░ ~90%
lint ██████████████░░░░░░ ~70%
 
────────────────────────────────────────────────────────────
context-engineer
01 The Problem

Your context window is leaking.

Claude Code consumes context on every tool call. Verbose test output, unfiltered build logs, full file reads when a grep would do. By the time you notice degradation, you've already lost coherence.

📋
Verbose Output
200+ lines of test/build output consumed when only 8 matter.
🔋
No Budget Awareness
No guardrails as context fills up. Same behavior at 20% and 90%.
📉
Silent Degradation
Claude starts forgetting, hallucinating, looping — and doesn't notice.
⚙️
Manual Model Switching
Using Opus for a file search. Haiku for architecture. No guidance.
PASS src/utils/format.test.ts PASS src/utils/date.test.ts PASS src/hooks/useAuth.test.ts PASS src/hooks/useTheme.test.ts PASS src/components/Button.test.tsx PASS src/components/Card.test.tsx PASS src/components/Modal.test.tsx PASS src/components/Nav.test.tsx PASS src/api/auth.test.ts PASS src/api/users.test.ts FAIL src/api/payments.test.ts ● should validate card number Expected: "4242...4242" Received: undefined PASS src/api/notifications.test.ts PASS src/store/cart.test.ts PASS src/store/user.test.ts ... 180+ more lines of passing tests ... Test Suites: 1 failed, 47 passed, 48 total Tests: 1 failed, 312 passed, 313 total
FAIL src/api/payments.test.ts ● should validate card number Expected: "4242...4242" Received: undefined Test Suites: 1 failed, 47 passed, 48 total Tests: 1 failed, 312 passed, 313 total ▶ context-engineer: 196 lines reduced to 8
Test output example (jest) ~80% token savings
02 What's Inside

9 techniques, one install.

Skills, hooks, commands, and agents working together to keep your context clean and your output sharp.

🟢
Budget Zones
GREEN/YELLOW/ORANGE/RED context usage zones with adaptive behavior.
Skill
🧠
Degradation Detection
Self-diagnosis when Claude starts forgetting or hallucinating.
Skill
🔍
Code Intelligence
Efficient tool selection — Grep vs Read, token cost awareness.
Skill
🔄
Model Switching
Task-to-model mapping. Haiku for search, Opus for architecture.
Skill
💭
Thinking Control
Calibrated reasoning depth — minimal to deep per task type.
Skill
🧪
Test Output Filter
Keeps FAIL/ERROR lines + summary. ~80% token savings.
Hook
🏗️
Build Output Filter
Keeps error/warning lines only. ~90% token savings.
Hook
🧹
Lint Output Filter
Keeps problem lines only. ~70% token savings.
Hook
📦
Fresh Context
TASK.md + PROGRESS.md handoff for seamless continuation.
Command
03 Token Savings

Measurable impact.

Three PostToolUse hooks automatically filter verbose Bash output. They only activate on output > 40 lines — short output passes through unfiltered.

Test Output (jest, vitest, pytest, go test, cargo test) ~80%
Strips passing tests, keeps failures + summary
Build Output (tsc, gradle, xcodebuild, cargo build) ~90%
Strips compilation noise, keeps errors + warnings
Lint Output (eslint, pylint, clippy, biome) ~70%
Strips clean files, keeps problem lines only
04 How It Works

Three steps. Two minutes.

1
Install the plugin
Two commands in your terminal. No config files, no dependencies beyond jq.
Terminal
# Add the marketplace claude plugin marketplace add silvesterdivas/context-engineer # Install the plugin claude plugin install context-engineer@context-engineer-marketplace
2
Run setup
Adds context engineering rules to your project's CLAUDE.md. Budget zones, tool efficiency, output filtering — all configured automatically.
Claude Code
/context-engineer:setup
3
Work normally
Background skills and hooks activate automatically. Budget zones adjust behavior as context fills. Output filters strip noise from every test, build, and lint run.
05 Commands Reference

Four slash commands.

CommandDescription
/context-engineer:setup Add context engineering rules to your project's CLAUDE.md. Run once per project.
/context-engineer:fresh-context Create TASK.md + PROGRESS.md with current progress. Use when context gets heavy.
/context-engineer:audit-mcp List MCP servers, estimate token overhead, flag unused ones wasting context.
/context-engineer:diagnose Health scorecard: CLAUDE.md, hooks, MCP hygiene, git state. Pass/warn/fail.
13 Installation

Get started now.

Two commands. No configuration. Works with any project.

Requires macOS, Linux, or Windows (via WSL). Needs jq installed.

Terminal
# Add the marketplace claude plugin marketplace add silvesterdivas/context-engineer # Install the plugin claude plugin install context-engineer@context-engineer-marketplace

Then run /context-engineer:setup in any project to configure it. Run /context-engineer:diagnose to verify.