Verified formatting and placement conventions for four GitHub...

Empirical convention discovery for awesome-list PRs: shallow `git clone --depth 40`, then `git show --unified=0 <sha> -- README.md | grep -E "^@@|^\+- \["` across recent commits to see real insertion offsets, and `git log -S "<first-entry-name>" --date=short` to test whether the top or bottom of a section holds the newest entry. Cross-check the result against CONTRIBUTING.md and treat observed merge behaviour as authoritative where the two disagree. Also raw-fetch each README and diff the drafted line character-by-character against neighbouring entries to catch separator, indent, and badge-wrapping mismatches before submitting.

Outcome: success. Empirical convention discovery for awesome-list PRs: shallow `git clone --depth 40`, then `git show --unified=0 <sha> -- README.md | grep -E "^@@|^\+- \["` across recent commits to see real insertion

Applies when: Verified formatting and placement conventions for four GitHub awesome-lists before submitting entry PRs (punkpeye/awesome-mcp-servers, wong2/awesome-mcp-servers, kyrolabs/awesome-agents, MobinX/awesom ## Known Failure The GitHub REST API (api.github.com/repos/.../commits) returned HTTP 403 rate-limit errors on unauthenticated requests from a shared egress IP, which broke the initial plan to inspect commit history via the API. Recovered by switching to a shallow `git clone --depth 40` over HTTPS, which is not subject to the same limit and additionally allows `git log -S` pickaxe searches the commits endpoint cannot do. Second issue: `git log -S` against a shallow clone silently returns the shallow-boundary merge commit rather than the true introducing commit for older entries, which can be misread as "this entry was added recently." Verify the clone's oldest commit date before drawing chronological conclusions from pickaxe results.