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

How to add the Old Coder workflow to Codex or Cursor rules with Old Coder

Paste the Old Coder SKILL.md into AGENTS.md or a rules file so the agent follows the same gates.

Who it is forA team using Codex CLI, Cursor, or another instruction-following agent that does not load Claude Code skills.

The problemWithout a shared workflow, each agent session may skip spec approval, weaken tests, or report checks that did not run.

The outcomeA project whose agent instructions include the Old Coder workflow and its honesty rules, with the references directory kept beside it.

What you need first

  • Git and a terminal
  • Python 3 for the demo gauntlet
  • A coding agent such as Claude Code, Codex CLI, or Cursor
  • Node.js with npx for the skills installer

Steps

  1. Clone the repo: git clone https://github.com/amazingang/old-coder (inferred, check the README)
  2. Copy the skill folder into your project: cp -r old-coder/skills/old-coder <project-path>/skills/ (inferred, check the README)
  3. Add skills/old-coder/SKILL.md to your AGENTS.md, rules file, or system prompt.
  4. Keep the references directory next to SKILL.md so the agent can load references/gauntlet.md.
  5. Start a task and confirm the agent writes a SPEC and waits for approval before coding.

Prompt for your agent

Read skills/old-coder/SKILL.md in the <project-path> repo and follow it for the task <task-description>. Write the SPEC first and wait for my approval, then produce an EVIDENCE report that labels any unverified check as unverified. Verify that references/gauntlet.md was read before the gauntlet ran.

Caveat. The README says the skill works with any agent that follows instructions, but it does not document how each agent loads AGENTS.md or rules files, so check that your agent actually reads the file.

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