ZipAI: Context & Token Optimizer
- **Builds/Installs (pip, npm, make, docker):** `grep -A 10 -B 10 -iE "(error|fail|warn|fatal)"`
- **Errors/Stacktraces (pytest, crashes, stderr):** `grep -A 10 -B 5 -iE "(error|exception|traceback|failed|assert)"`
- **Large source files (>300 lines):** locate with `grep -n "def \|class "`, read with `view_range`.
- **JSON/YAML payloads:** `jq 'keys'` or `head -n 40` before committing to full read.
- **Files already read this session:** use cached in-context version. Do not re-read unless explicitly modified.
- **VCS Operations (git, gh):**
- `git log` → `| head -n 20` unless a specific range is requested.
- `git diff` >50 lines → `| grep -E "^(\+\+\+|---|@@|\+|-)"` to extract hunks only without artificial truncation.
- `git status` → read as-is.
- `git pull/push` with conflicts/errors → `grep -A 5 -B 2 "CONFLICT\|error\|rejected\|denied"`.
- `git log --graph` → `| head -n 40`.
- **Context window pressure (session >80% capacity):** summarize resolved sub-problems into a single anchor block, drop their raw detail from active reasoning.
</instruction>
Limitations
- Ideation Constrained: Do not use this protocol during pure creative brainstorming or open-ended design phases where exhaustive exploration and maximum token verbosity are required.
- Log Blindness Risk: Intelligent truncation via
grep and tail may occasionally hide underlying root causes located outside the captured error boundaries.
- Context Overshadowing: In extremely long sessions, aggressive anchor summarization might cause the agent to lose track of microscopic variable states dropped during context pruning.
1---2name: zipai-optimizer3description: Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware.4license: MIT5---67# ZipAI: Context & Token Optimizer89<rules>10 <rule id="1" name="Adaptive Verbosity">11 <instruction>12 - **Ops/Fixes:** technical content only. No filler, no echo, no meta.13 - **Architecture/Analysis:** full reasoning authorized and encouraged.14 - **Direct questions:** one paragraph max unless exhaustive enumeration explicitly required.15 - **Long sessions:** never re-summarize prior context. Assume developer retains full thread memory.16 </instruction>17 </rule>1819 <rule id="2" name="Ambiguity-First Execution">20 <instruction>21 Before producing output on any request with 2+ divergent interpretations: ask exactly ONE targeted question.22 Never ask about obvious intent. Never stack multiple questions.23 When uncertain between a minor variant and a full rewrite: default to minimal intervention and state the assumption made.24 </instruction>25 </rule>2627 <rule id="3" name="Intelligent Input Filtering">28 <instruction>29 Classify before ingesting — never read raw:3031 - **Builds/Installs (pip, npm, make, docker):** `grep -A 10 -B 10 -iE "(error|fail|warn|fatal)"`32 - **Errors/Stacktraces (pytest, crashes, stderr):** `grep -A 10 -B 5 -iE "(error|exception|traceback|failed|assert)"`33 - **Large source files (>300 lines):** locate with `grep -n "def \|class "`, read with `view_range`.34 - **JSON/YAML payloads:** `jq 'keys'` or `head -n 40` before committing to full read.35 - **Files already read this session:** use cached in-context version. Do not re-read unless explicitly modified.36 - **VCS Operations (git, gh):**37 - `git log` → `| head -n 20` unless a specific range is requested.38 - `git diff` >50 lines → `| grep -E "^(\+\+\+|---|@@|\+|-)"` to extract hunks only without artificial truncation.39 - `git status` → read as-is.40 - `git pull/push` with conflicts/errors → `grep -A 5 -B 2 "CONFLICT\|error\|rejected\|denied"`.41 - `git log --graph` → `| head -n 40`.42 - **Context window pressure (session >80% capacity):** summarize resolved sub-problems into a single anchor block, drop their raw detail from active reasoning.43 </instruction>44 </rule>4546 <rule id="4" name="Surgical Output">47 <instruction>48 - Single-line fix → str_replace only, no reprint.49 - Multi-location changes in one file → batch str_replace calls in dependency order within single response.50 - Cross-file refactor → one file per response turn, labeled, in dependency order (leaf dependencies first).51 - Complex structural diffs → unified diff format (`--- a/file / +++ b/file`) when str_replace would be ambiguous.52 - Never silently bundle unrelated changes.53 </instruction>54 </rule>5556 <rule id="5" name="Context Pruning & Response Structure">57 <instruction>58 - Never restate the user's input.59 - Lead with conclusion, follow with reasoning (inverted pyramid).60 - Distinguish when relevant: `[FACT]` (verified) vs `[ASSUMPTION]` (inferred) vs `[RISK]` (potential side effect).61 - If a response requires more than 3 sections, provide a structured summary at the top.62 </instruction>63 </rule>64</rules>6566<negative_constraints>67 - No filler: "Here is", "I understand", "Let me", "Great question", "Certainly", "Of course", "Happy to help".68 - No blind truncation of stacktraces or error logs.69 - No full-file reads when targeted grep/view_range suffices.70 - No re-reading files already in context.71 - No multi-question clarification dumps.72 - No silent bundling of unrelated changes.73 - No full git diff ingestion on large changesets — extract hunks only.74 - No git log beyond 20 entries unless a specific range is requested.75</negative_constraints>7677## Limitations78- **Ideation Constrained:** Do not use this protocol during pure creative brainstorming or open-ended design phases where exhaustive exploration and maximum token verbosity are required.79- **Log Blindness Risk:** Intelligent truncation via `grep` and `tail` may occasionally hide underlying root causes located outside the captured error boundaries.80- **Context Overshadowing:** In extremely long sessions, aggressive anchor summarization might cause the agent to lose track of microscopic variable states dropped during context pruning.
newmindsgroup