harness-context-budget

Audits OpenCode and Cursor context load from skills, plugins, commands, and MCPs.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-context-budget-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-context-budget
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-context-budget
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-context-budget-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large PREVC work in OpenCode or Cursor can suffer from excessive context pressure when too many skills, plugins, commands, MCPs, and always-loaded instructions compete for the model's context window. This Skill audits that load so you can reduce context pressure and attack surface before starting heavy work. ## Core Features & Use Cases - Context Load Audit: Runs a Node.js script that reports context consumption from skills, plugins, commands, MCPs, and always-loaded instructions. - Reduction Guidance: Recommends lazy-loading task-specific skills, preferring scripts over always-on MCPs for audits, and keeping Cursor parity minimal without duplicating /goal state. - Use Case: Before kicking off a large PREVC planning and execution cycle, run the audit to identify which always-on components can be disabled or lazy-loaded to free context budget. ## Quick Start Ask the agent to run the harness context budget audit and report which skills, plugins, and MCPs are consuming context before starting a large PREVC task.

Frequently Asked Questions about harness-context-budget

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit context usage in OpenCode before a large task?

Run the harness-context-budget script with node .opencode/scripts/harness-context-budget.mjs. It reports context load from skills, plugins, commands, MCPs, and always-loaded instructions so you can decide what to disable or lazy-load.

How to reduce context pressure from MCP servers in OpenCode?

Prefer running audits through one-off scripts instead of keeping always-on MCP servers connected. The audit report identifies which MCPs consume context so you can replace them with on-demand script execution.

Should skills be always loaded or lazy-loaded in OpenCode?

Task-specific skills should be lazy-loaded rather than always loaded. Lazy-loading keeps the context window free for the active PREVC work, and the audit report shows which skills contribute to baseline context load.

Does this audit work with Cursor as well as OpenCode?

Yes, the audit covers both OpenCode and Cursor context sources. The guidance recommends keeping Cursor parity minimal and avoiding duplication of /goal state between the two environments.

When should I run a context budget audit?

Run it before starting large PREVC planning, execution, or validation work. Auditing early prevents context overflow mid-task and reduces the attack surface from unnecessary always-on components.