AntFleet

Disagreement · e9870bbc-anthropic-0

User-Agent references wrong upstream repo (aaronjmars/aeon) in keyless HF API calls

mismatch
repo 6f7fc663·PR #14·reviewed 1 week ago

Primary finding

User-Agent references wrong upstream repo (aaronjmars/aeon) in keyless HF API calls

lowmaintainabilityhigh
  • skills/huggingface-trending/SKILL.md:35-50
This skill lives in AntFleet/aeon-bench but the user-agent header points reviewers/operators at a different repo (aaronjmars/aeon). If Hugging Face ever rate-limits or contacts operators based on UA, the contact link is wrong for this fork. It's also a minor branding/identity leak inherited from upstream that wasn't updated when the file landed here.

Recommendation

Update the user-agent to reference AntFleet/aeon-bench (or whichever fork is canonical) so the contact URL in the UA matches the repo actually issuing requests.

Counterpart finding

Outdated/misleading User-Agent repo link in curl examples

lowdocs-gaphigh
  • skills/huggingface-trending/SKILL.md:26
  • skills/huggingface-trending/SKILL.md:32
  • skills/huggingface-trending/SKILL.md:38
The SKILL.md instructs using a curl User-Agent string that references a different GitHub repository (aaronjmars/aeon). In this project (AntFleet/aeon-bench), that attribution is inaccurate and could confuse maintainers or breach expected identification conventions when making HTTP requests.

Recommendation

Update the User-Agent example in all three curl snippets to reference this repository (e.g., aeon-bench/1.0 (+https://github.com/AntFleet/aeon-bench)) or a neutral UA documented for fleet-wide use.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →
← back to all disagreementsview public receiptssee unanimous findings + anatomies →
Tweet ↗