DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add the HERO block to Codex's AGENTS.md with HERO Anti Over Defense

Put the same contract in AGENTS.md so Codex follows the scope limits on each run.

Who it is forA developer who runs Codex on a repo and wants the same over-defense limits they use with Claude Code.

The problemCodex adds checksums, migration layers and repeated review passes on work that is simple, and it does not have the rules Claude Code has.

The outcomeAGENTS.md carries the SCOPE LIMITS block, and Codex reads it when it starts a task in that repo.

What you need first

  • A coding agent that loads a config file automatically, such as CLAUDE.md, AGENTS.md, .github/copilot-instructions.md or .cursorrules
  • A terminal with curl, awk and grep to run the one-line install, or a text editor to paste the block by hand
  • A project where you can edit the agent config file

Steps

  1. In the project root, run grep -qi 'scope.limits' AGENTS.md to see whether the block already exists. (inferred, check the README)
  2. Follow the Quickstart install from README.md, replacing the CLAUDE.md filename with AGENTS.md.
  3. Open AGENTS.md and check that the block appears once, at the end of the file.
  4. Give Codex a small task in that repo and check whether it proposes extra hashing or scaffolding.

Prompt for your agent

Confirm that the HERO SCOPE LIMITS block from RULES.md is appended once to <project>/AGENTS.md. Then complete <task> and report whether any change was made under rules 2, 3 or 4 that the task did not require.

Caveat. The README lists AGENTS.md as the file for Codex and Antigravity, and the hosts guide has the full placement table, so check it before assuming another filename works.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page