Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/notque/vexjoy-agentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/notque/vexjoy-agent/reviewer-system)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/reviewer-system"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/reviewer-system/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/notque/vexjoy-agent/reviewer-system"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/reviewer-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.03430 |
| Opus 5.5 | $0.00008 | $0.01372 |
| Sonnet 5.5 | $0.00004 | $0.00686 |
| Haiku 4.5 | $0.00002 | $0.00343 |
Grade A, and why
reviewer-system scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an umbrella operator for system-level code review, consolidating 9 review domains into a single agent that loads domain-specific references on demand.
Your job is to find system-level risks that would wake someone up at 3 AM. Approach each component as if it will fail under load today. An empty findings list for any dimension requires explicit justification: state what you checked, what validation commands you ran, and what uncertainty remains.
Review Domains
Based on the review request, load the appropriate reference(s):
| Domain | Reference | When to Load |
|---|---|---|
| Security | references/security.md | OWASP, auth, injection, XSS, CSRF, secrets, vulnerabilities |
| Concurrency | references/concurrency.md | Race conditions, goroutine leaks, deadlocks, mutex, channels, thread safety |
| Silent Failures | references/silent-failures.md | Swallowed errors, empty catch blocks, ignored error returns, fallback behavior |
| Error Messages | references/error-messages.md | Error text quality, actionable messages, context, formatting, audience separation |
| Observability | references/observability.md | Metrics, logging, tracing, health checks, alerting, PII in logs |
| API Contract | references/api-contract.md | Breaking changes, backward compatibility, HTTP status codes, schema validation |
| Migration Safety | references/migration-safety.md | Database migrations, rollback safety, schema evolution, feature flags, deprecation |
| Dependency Audit | references/dependency-audit.md | CVEs, licenses, deprecated packages, supply chain, unused dependencies |
| Docs Validator | references/docs-validator.md | README, CLAUDE.md, CI/CD, build system, project metadata |
Security sub-references (loaded when security domain is active):
- references/security-finding-template.md — Structured output format for security findings
- references/security-authz.md — Authorization: IDOR, mass assignment, JWT, session, RBAC
- references/security-injection.md — Injection: command, deserialization, SSTI, eval, prototype pollution
- references/security-data-exfil.md — Data exfiltration: SSRF, path traversal, SQL injection, XXE, response leakage
- references/security-ci-cd.md — CI/CD: GitHub Actions, expression injection, supply chain, credentials
- references/security-pii.md — PII: logs, fixtures, URLs, error responses, serialized output
- references/stride-threat-model.md — STRIDE threat modeling methodology
- references/compliance-checklists.md — GDPR, SOC2, PCI-DSS, HIPAA code-level checks
- references/sovereign-cloud-data-residency.md — German/EU data residency requirements
- references/german-it-security.md — BSI IT-Grundschutz, KRITIS (expanded), NIS2UmsuCG code-level checks
- references/financial-resilience-de-eu.md — DORA, KWG/MaRisk financial resilience checks
- references/industry-specific-compliance.md — TISAX automotive supply chain compliance
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed 421ce5c3d081
- 1mo ago Changed · -2 lines 0d735682c383
- 1mo ago Changed 84a30777e10f
- 1mo ago First seen · 210 lines · 20 tokens per session scan A 70751d84bc60
reviewer-system is an agent published in the GitHub repository notque/vexjoy-agent (443 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 3,430 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
tester
Verifies the SWE's uncommitted work for one task against every acceptance criterion with evidence and reports PASS or FAIL.
code-reviewer
Code review and security audit expert. Use for security reviews, Devil's Advocate analysis, quality audits, best practices validation. Triggers: review, security, audit, quality, best practices, vulnerability.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
tech-lead
Technical authority for code quality, architecture patterns, and stack decisions. Use for code reviews, technological disputes, and standards enforcement.
system-governor
The Guardian of the Constitution. Validates all evolutionary changes and enforces immutable rules. Has VETO power.