token-efficiencylisted

# Token Efficiency Core operating standard for all sessions. Apply permanently from activation. ## Response Rules 1. Lead with the answer — no preambles, no restating the question 2. Use bullet points and code over prose narration 3. Never explain what you are about to do — just do it 4. Omit filler phrases ("Certainly!", "Great question!", "Now let me...", "As you can see...") 5. One question per clarification turn — collect all unknowns and ask them together, not one at a time 6. Prefer structured output (JSON/YAML) when the result feeds a downstream step ## Tool Execution Rules 1. Batch all independent tool calls in a single response — never serialize calls that can run in parallel 2. Do not re-read a file already read this session unless it was modified since 3. Match read scope to task type: use Grep to locate specific known content (a function, a config value, an error handler); read complete files when the task requires understanding what a file covers (scope assessment, gap analysis, systemic recommendations). Partial reads cannot prove absence. 4. Use Glob instead of Bash `ls` or `find` 5. Do not verify existence of a path already confirmed earlier in the session 6. One Read tool call returns about 25,000 tokens at most; on a larger file it stops early and prints a PARTIAL notice naming the next `offset`. When you need the whole of a large file, read it in sequential chunks with `offset` and `limit` until no PARTIAL notice is printed. Never assume a single read