Add praetor to Plugins & Extensions

[luoxianzi]

Adds praetor — what sets it apart from the first-party codex bridge: a binding, independent, fresh-context judge. Acceptance criteria are frozen in git before the executor runs, and the judge — which never saw the planning conversation — returns a PASS/FAIL the planner cannot override. Legion Mode runs 2–5 parallel Codex workers in isolated git worktrees behind a mandatory integration judge (2.84× measured on a real 3-lane run). Zero-config; the README benchmark table includes its own failures on purpose. MIT.

Repo: https://github.com/luoxianzi/praetor · Why-a-judge write-up: https://github.com/luoxianzi/praetor/blob/main/docs/WHY-A-JUDGE.md

🤖 Generated with Claude Code

[qodo-code-review]

PR Summary by Qodo

Add praetor to Plugins & Extensions list

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Add praetor to the Plugins & Extensions table.
• Describe praetor’s multi-agent flow with a binding, fresh-context judge.
• Link to the praetor GitHub repository for installation and details.

High-Level Assessment

The PR’s approach is optimal for this repo’s goal (a curated list): add a single concise table entry with a direct link and a one-line differentiator. Alternatives (e.g., adding a separate subsection or longer blurb) would add noise without improving discoverability.

Files changed (1) +1 / -0

Documentation (1) +1 / -0

README.mdAdd praetor entry to Plugins & Extensions table +1/-0

Add praetor entry to Plugins & Extensions table

• Adds a new row linking to the praetor repository and summarizing its judge-based, multi-agent orchestration model (planner/executor separation, acceptance criteria frozen in git, parallel workers with integration judge).

README.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Stale status metrics 🐞 Bug ≡ Correctness

Description

README.md’s Status table still reports "Plugins listed | 4" and "Last updated | 2025-Q2" even though
the Plugins & Extensions table now contains 5 plugin entries after adding praetor, making the status
section inaccurate.

Code

README.md[33]

+| [praetor](https://github.com/luoxianzi/praetor) | luoxianzi | Claude plans, the Codex CLI executes, and a binding fresh-context judge decides what merges — acceptance criteria frozen in git before the executor runs; Legion Mode runs 2–5 parallel workers behind an integration judge |

Evidence

The Status section explicitly claims 4 plugins and a 2025-Q2 update, but the Plugins & Extensions
table lists five rows (including the newly added praetor), so the status values are incorrect after
this change.

README.md[7-13]
README.md[25-34]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README Status table is now inconsistent with the actual number of plugin entries after adding the praetor row.

## Issue Context
The PR adds a 5th plugin entry but the Status section still states 4 plugins and an older "Last updated" value.

## Fix Focus Areas
- README.md[7-13]
- README.md[25-34]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Stale status metrics 🐞 Bug ≡ Correctness

README.md’s Status table still reports "Plugins listed | 4" and "Last updated | 2025-Q2" even though
the Plugins & Extensions table now contains 5 plugin entries after adding praetor, making the status
section inaccurate.

Agent Prompt

## Issue description
The README Status table is now inconsistent with the actual number of plugin entries after adding the praetor row.

## Issue Context
The PR adds a 5th plugin entry but the Status section still states 4 plugins and an older "Last updated" value.

## Fix Focus Areas
- README.md[7-13]
- README.md[25-34]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools