by syabro · Agent Tool · ★ 166
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
npm install -g rejudge
npx skills add syabro/rejudge -g -y
Taken from the project's README on GitHub. Check the security audit before running it.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 166 |
| Forks | 16 |
| Language | TypeScript |
| Category | Agent Tool |
| License | MIT |
| Quality Score | 67/100 |
| Last Updated | 2026-10-08 |
| Created | 2026-07-15 |
| Platforms | node |
| Est. Tokens | ~16k |
Rejudge Two heads are better than one. Several models and a judge dig deeper. Independent second opinion for your agent. One npm package gives you three ways to run it: the command, a native Pi tool, and an Agent Skill for coding agents outside Pi. More at rejudge.syabro.com. Why several models There are four ways to check code an agent wrote. Each one catches more than the last. I.
Looking for a rejudge alternative? If you're comparing rejudge with other agent tool tools, these 1 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
Lightweight registry to discover, install, and manage all public Claude plugins and agent skills for your favo
Explore other popular agent tool tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: