I'd be interested to see results with Opus 4.6 or 4.5

Also, I bet the quality of these docs vary widely across both human and AI generated ones. Good Agents.md files should have progressive disclosure so only the items required by the task are pulled in (e.g. for DB schema related topics, see such and such a file).

Then there's the choice of pulling things into Agents.md vs skills which the article doesn't explore.

I do feel for the authors, since the article already feels old. The models and tooling around them are changing very quickly.

▲

deaux 5 hours ago | parent | next [-]

Agree that progressive disclosure is fantastic, but

> (e.g. for DB schema related topics, see such and such a file).

Rather than doing this, put another AGENTS.md file in a DB-related subfolder. It will be automatically pulled into context when the agent reads any files in the file. This is supported out of the box by any agent worth its salt, including OpenCode and CC.

IMO static instructions referring an LLM to other files are an anti-pattern, at least with current models. This is a flaw of the skills spec, which refers to creating a "references" folder and such. I think initial skills demos from Anthropic also showed this. This doesn't work.

	▲	prodigycorp 3 hours ago \| parent [-]
		This is probably the best comment in the thread. I've totally forgotten about nested AGENTS.md files, gonna try implementation today.

▲

dpkirchner 18 hours ago | parent | prev [-]

Progressive disclosure is good for reducing context usage but it also reduces the benefit of token caching. It might be a toss-up, given this research result.

	▲	deaux 5 hours ago \| parent [-]
		Those are different axes - quality vs money. Progressive disclosure is invaluable because it reduces context rot. Every single token in context influences future ones and degrades quality. I'm also not sure how it reduces the benefit of token caching. They're still going to be cached, just later on.