mcp-economy

Enforce cost-aware MCP usage to minimize token burn.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/opzero1/op1 --skill mcp-economy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-economy
Source: https://github.com/opzero1/op1/tree/main/packages/install/templates/skill/mcp-economy
Command: npx skills add https://github.com/opzero1/op1 --skill mcp-economy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reduce token costs by preventing unnecessary external lookups and by encouraging local reasoning first.

Core Features & Use Cases

  • MCP gating: Only invoke external tools when local context is insufficient.
  • Cost-aware decisions: Prioritize lightweight lookups (context7, small queries) before heavier searches.
  • Use Case: When a task could require broad web search, apply this skill to decide whether to search or work offline.

Quick Start

In your task prompt, state: 'Prioritize local context; use MCPs only if necessary.'

Frequently Asked Questions about mcp-economy

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

FAQPage Schema
How do I minimize token burn during MCP web searches?

To minimize token burn during MCP web searches, you should enforce cost-aware usage by prioritizing local context and only invoking external tools when local reasoning is insufficient.

What is MCP gating for context management?

MCP gating for context management is a strategy that prevents unnecessary external lookups by checking if local context is sufficient before allowing external tools to execute.

When should I rely on local context versus MCPs?

You should rely on local context versus MCPs whenever a task can be completed offline, only triggering external tools for broad web searches or context expansion if local data is inadequate.

Does prioritizing lightweight lookups reduce token costs?

Prioritizing lightweight lookups like context7 and small queries reduces token costs by preventing heavy external tools from executing before cost-aware decisions are fully evaluated.

How do I cap expensive queries to stay within token budgets?

You can cap expensive queries to stay within token budgets by applying a lightweight MCP strategy that restricts broad web searches and forces the system to evaluate local context first.

Why does my task trigger heavy external tools instead of local reasoning?

Your task triggers heavy external tools instead of local reasoning because it lacks a cost-aware MCP strategy to gate external lookups and prioritize local context for token optimization.