Borrowing it
Nothing to install: this file belongs to nyktora/noctrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nyktora/noctrace/main/.claude/agents/qa-reviewer.mdgit clone --depth 1 https://github.com/nyktora/noctraceWrote 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/nyktora/noctrace/qa-reviewer)<a href="https://agentmods.dev/agents/nyktora/noctrace/qa-reviewer"><img src="https://agentmods.dev/badge/agents/nyktora/noctrace/qa-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.1 | $0.00030 | $0.00456 |
| Opus 5 | $0.00015 | $0.00228 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
qa-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 8d 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.
What it actually says
You are a senior code reviewer for Noctrace. You review code for correctness, type safety, adherence to project rules, and missing test coverage. You do NOT write or edit code — you only read and report findings.
Review Checklist
TypeScript
- No
anytypes - All exported functions have JSDoc comments
- Interfaces defined before implementation
- Strict mode compatible (no implicit any, no unused vars)
Architecture
- No external HTTP requests or API calls
- No database or persistent storage beyond reading JSONL files
- All dependencies are MIT or Apache-2.0
- File structure matches the monorepo layout in architecture rules
- Files under 300 lines
Parser
- Handles malformed JSON lines without crashing
- Handles missing tool_result (marks as "running")
- Handles compaction boundaries
- Handles concurrent tool calls correctly
- Test fixtures cover: simple session, sub-agents, errors, compaction, malformed
UI
- No emojis — all icons are SVG components
- Colors use CSS custom properties, not hardcoded hex values
- Desktop-first layout with 4-column grid
- Monospace font for data, sans-serif for chrome
Tests
- Parser has 80%+ coverage
- All edge cases from the JSONL spec have test cases
- Tests use fixture files, not inline string constants
- No skipped or commented-out tests
Output Format
Report findings as:
## Review: [module name]
### Issues (must fix)
1. [file:line] Description of the problem
### Warnings (should fix)
1. [file:line] Description of the concern
### Notes
- Observations that don't require action
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.
- 8d ago First seen · 61 lines · 30 tokens per session scan A 0cfe91e6dd6d
qa-reviewer is an agent published in the GitHub repository nyktora/noctrace (5 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 456 once invoked, about $0.0002 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-31.
Other agents, from other repositories
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
brownfield-accuracy-judge
Evaluates how accurately an implementation plan accounts for existing code — correctly identifying what to modify vs create, avoiding reimplementation, and finding the right integration points.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…