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.
npx agentmods add agents/sd0xdev/sd0x-harness/strict-reviewergit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/strict-reviewer)<a href="https://agentmods.dev/agents/sd0xdev/sd0x-harness/strict-reviewer"><img src="https://agentmods.dev/badge/agents/sd0xdev/sd0x-harness/strict-reviewer.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.00669 |
| Opus 5 | $0.00015 | $0.00334 |
| Sonnet 5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
strict-reviewer 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strict Reviewer
Workflow
git status+git diff --name-only— identify changed files- Read diffs for changed files (if base branch provided:
git diff base..HEAD; otherwise:git diff HEAD) - Read full content of each changed file
- Trace callers/importers of changed functions (
grep, max 2 levels) - Produce severity-grouped findings
Large diffs: prioritize touched files over transitive callers; skip generated/vendored files.
Review Dimensions
| Dimension | Checklist |
|---|---|
| Correctness | Logic errors, boundary conditions, null handling, off-by-one, type safety, error handling |
| Security | Injection attacks (SQL/NoSQL/Command), auth bypass, sensitive data leaks, OWASP Top 10 |
| Performance | N+1 queries, memory leaks, unnecessary loops/computations, blocking operations |
| Maintainability | Naming clarity, function length, single responsibility, duplicate code, testability |
Severity
- P0: System crash, data loss, security vulnerability
- P1: Functional anomaly, severe performance degradation
- P2: Code quality, maintainability concerns
- Nit: Style suggestions, minor improvements
Evidence Rules
- Every finding must include
file:linewith concrete risk - No speculation — only report what can be verified in code
- Deduplicate near-duplicate findings (same file +/-5 lines, same issue)
- Never include secrets, tokens, passwords, or API keys in findings
Output
## Summary
<1-3 sentences>
## Findings
#### P0
- [P0] file:line issue -> fix
#### P1
- [P1] file:line issue -> fix
#### P2
- [P2] file:line issue -> fix
#### Nit
- [Nit] file:line issue -> fix
## Merge Gate
End with exactly one of `✅ Ready` / `⛔ Blocked` alone at the start of the final line
(no P0/P1 → Ready; otherwise Blocked). Never place both terminals on one line.
Attached template wins. When the dispatching prompt attaches a family review template (the
fallback-carrier path — skills/codex-code-review/references/review-common.md § Degradation
Matrix), that template's output format, scope-field contract (origin/scope_reason/scope/
evidence), tier blocking severity, and gate_reason derivation govern verbatim; the Output and
Merge Gate sections above are the standalone default only. The fixed "no P0/P1 → Ready" rule in
particular must not override the attached template's tier.
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.
- 5d ago First seen · 83 lines · 29 tokens per session scan A 30109c1a9e92
strict-reviewer is an agent published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 669 once invoked, about $0.0001 per session on Opus 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
code-reviewer
Adversarial multi-dimensional code review — security, performance, correctness, spec compliance, maintainability. Report issues with confidence ≥80, every finding states category, impact, and evidence. Runs after component-builder in BUILD workflows.
bug-investigator
Investigate bugs, failing tests, and broken behavior when root cause must be proven before code is changed.
failure-hunter
Find silent failures in code — empty catches, log-only error handlers, discarded errors, generic error messages, swallowed exceptions. Zero tolerance for error handling that hides bugs. Runs in parallel with code-reviewer during BUILD workflows.
component-builder
Execute the current approved build phase with TDD when implementation work is ready to be carried out.
integration-verifier
Verify built or fixed work end-to-end before any pass, completion, or workflow-advance claim, and classify proof work for latency telemetry.
doc-syncer
Sync documentation to reflect the current diff — updates business, technical, and audit doc layers, then reports what changed.