cd /news/ai-agents/benchmarking-affaan-m-ecc-in-cursor-… · home topics ai-agents article
[ARTICLE · art-131954] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Benchmarking affaan-m/ECC in Cursor: Agent Harness Rules Without Context Exhaustion

A developer documented a modular setup for running the affaan-m/ECC agent harness inside Cursor, symlinking only common and TypeScript rules into .cursor/rules/ and registering ECC's MCP servers via .cursor/mcp.json to avoid context bloat. The writeup claims that routing Cursor through B-Lost's proxy endpoint, which offers gateway-level prompt caching, cut heavy multi-turn context costs by roughly 80-90% without losing chat history or degrading reasoning fidelity.

by read2 min views1 publishedSep 16, 2026

When evaluating affaan-m/ECC (v2.0, The Agent Harness Operating System), the main attraction is standardization. Instead of manually copying fragmented .cursorrules, skill prompts, and MCP configurations between Claude Code, Codex, and Cursor, ECC packages skills, instincts, and execution policies into a unified harness.

However, bringing an enterprise-grade agent harness into Cursor introduces a familiar bottleneck: context bloat. Stacking dense instinct files, language-specific rules, and MCP tool schemas into your agent's system prompt burns tokens rapidly. In deep multi-turn refactoring loops, this degrades model reasoning and inflates per-turn API latency.

Here is how we set up ECC modularly inside Cursor and stabilized multi-turn session costs.

Avoid dumping all ECC skills into Cursor's root prompt. Instead, install the repository and link only the target language rules into .cursor/rules/:

git clone https://github.com/affaan-m/ECC.git ~/.config/ecc

mkdir -p .cursor/rules
cp ~/.config/ecc/rules/common/*.mdc .cursor/rules/
cp ~/.config/ecc/rules/typescript/*.mdc .cursor/rules/

This keeps your baseline context lightweight, injecting language rules only when matching files are active.

ECC defines modular MCP servers for test runners and filesystem inspections. Add them to your project's .cursor/mcp.json:

{
  "mcpServers": {
    "ecc-harness": {
      "command": "npx",
      "args": ["-y", "@ecc/harness-mcp@latest"]
    }
  }
}

Every time Cursor executes an agentic cycle (read file → invoke MCP → patch code), it resends the entire conversation history along with ECC's static rules. On vanilla endpoints, you pay full token rates on every re-evaluation.

In our tests, switching Cursor to B-Lost's fast proxy endpoint resolved this bottleneck. Because B-Lost provides native prompt caching at the gateway layer, static harness rules and accumulated turn history are cached automatically. This cut heavy multi-turn context costs by ~80-90% without losing chat history or degrading reasoning fidelity.

// ~/.cursor/settings.json (Custom Model Override)
{
  "cursor.customModel.override": true,
  "cursor.customModel.baseUrl": "https://api.b-lost.com/v1",
  "cursor.customModel.model": "claude-3-7-sonnet-20250219"
}

affaan-m/ECC provides a disciplined framework for managing agent instincts. The key to running it inside Cursor without slowdowns is modular rule scoping combined with gateway-level prompt caching.

── more in #ai-agents 4 stories · sorted by recency
── more on @affaan-m/ecc 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/benchmarking-affaan-…] indexed:0 read:2min 2026-09-16 ·