Claude Opus 5 prompt tips say old harness habits now waste tokens
tengyanAI · x · 2026-07-25
A user shares prompting notes for Claude Opus 5 after testing it in agent-style workflows.
Their main takeaways: avoid redundant instructions like asking the model to verify or double-check, because it may already do that internally; don’t spawn subagents just to review its own work; and if you want concise output, say so explicitly. The post also suggests giving the model the full task up front and letting it run, since effort controls reasoning rather than verbosity.
Related event: Claude Opus 5 Early Tests: Better Efficiency but Overly Proactive(29 posts)→
More from coding & agent
- 10 practical ways to run Astra computer use on Premiere Pro for video editing — beechinour · 2026-10-27
- Dev ships a delightful free shadcn UI for agent run and tool-call traces — round · 2026-10-27
- Phil Schmid launches Gemini API CLI: a stateless multimodal tool belt for your existing coding agent — _philschmid · 2026-10-27
- Musk hails Grok Bot as 'incredibly competent chief of staff' as user automates inbox triage — elonmusk · 2026-10-27
- shadcn's /improve skill paired with Grok on SuperGrok Heavy for plowing through issues — shadcn · 2026-10-27
- Paradigm Launches Envoys: Your Claude Code and Codex on Your Research Graph, Free — tensorqt · 2026-10-27