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

How to rerun the demo gauntlet to check the evidence yourself with Old Coder

Run the full gauntlet on the included rate limiter and confirm the reported numbers.

Who it is forA reviewer who wants to check the demo's claimed 41 tests, 100% coverage, and 22/22 planted bugs caught before trusting the approach.

The problemA report of green checks means little unless you can rerun the same checks yourself.

The outcomeA fresh local run of the gauntlet that reproduces the report, with results you produced rather than the ones written in evidence.md.

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 and open it: git clone https://github.com/amazingang/old-coder then cd old-coder (inferred, check the README)
  2. Enter the demo folder: cd demo-rate-limiter
  3. Create the environment and install: python3 -m venv .venv && .venv/bin/pip install -r requirements-dev.txt -e .
  4. Run the whole report: ./tools/gauntlet.sh
  5. Compare the output with evidence.md and note any difference in test count, coverage, or mutation results.

Prompt for your agent

In the old-coder repo, go to demo-rate-limiter and run ./tools/gauntlet.sh after setting up .venv as the README describes. Report the test count, statement and branch coverage, and planted bugs caught, and state whether each matches evidence.md.

Caveat. The demo is a rate limiter, and the README says the gauntlet cannot prove the spec is complete, so a green run shows only the constraints the demo encodes.

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