@mattpocockuk: 90% of people can delete their AGENTS.md and their output will improve. Use it as an index of pointers to important fil…
Summary
Matt Pocock suggests that most people should delete their AGENTS.md file and use it only as an index of pointers to important files, pruning aggressively to improve output.
View Cached Full Text
Cached at: 07/04/26, 10:53 PM
@humblyonline 90% of people can delete their AGENTS.md and their output will improve.
Use it as an index of pointers to important files, and even then aggressively prune it for no-ops.
How’s that for vague
Similar Articles
@mattpocockuk: Prompt of the day: /writing-for-agents my AGENTS.md is a hot mess, propose a series of restructurings that: - Remove no…
Matt Pocock shares a 'prompt of the day' for cleaning up a messy AGENTS.md: remove no-ops, use progressive disclosure, and move instructions to CODING_STANDARDS.md, delegating the work across three increasingly radical subagents into a single PR. He argues AGENTS.md files are the biggest source of token inefficiency in agent workflows.
@thomaszhou_: Really useful best practices! Optimizing AGENTS.md is something almost everyone can benefit from. I picked out a few common scenarios from the article and pasted the prompts here so you can copy and use them directly: 1. Scientifically optimize your AGENTS.md Prompt: Review my recent Codex sessions and find a...
A tweet sharing best practices for AGENTS.md optimization and dead code cleanup, with ready-to-copy prompts. It covers use cases of cleaning up 800K+ lines of dead code with GPT-6 Astra + Codex, and optimizing CI duration with GPT-6.1 Sol.
@kentcdodds: Claude Code cut about 80% of its system prompt for newer models. A research paper evaluating AGENTS.md found those file…
Kent C. Dodds discusses a research paper showing AGENTS.md often doesn't improve task success while adding over 20% inference cost, and asks what should actually be placed in AGENTS.md, noting Claude Code reduced its system prompt by 80%.
@mattpocockuk: Prompt of the day: /retro read my last 10 coding agent sessions and find ways to make my repo easier to navigate. Find …
Matt Pocock shares a 'prompt of the day' that uses a retrospective review of recent coding agent sessions to spot where agents struggle to find information or rely on stale docs, arguing that improving repo navigability is an underrated way to save tokens.
I deleted 71% of my agent instruction files across 6 repos. Here's what was actually in the pile.
A developer shares their audit of Claude Code agent instruction files, removing 71% of them and categorizing the bloat, offering a rubric for deciding what to keep and a script to measure instruction footprint.