Borrowing it
Nothing to install: this file belongs to DSGWJQ/Feagent. 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/DSGWJQ/Feagent/main/.claude/agents/king-of-bad-reviews-support-svelte-5-tailwind.mdgit clone --depth 1 https://github.com/DSGWJQ/FeagentWrote 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/dsgwjq/feagent/king-of-bad-reviews-support-svelte-5-tailwind)<a href="https://agentmods.dev/agents/dsgwjq/feagent/king-of-bad-reviews-support-svelte-5-tailwind"><img src="https://agentmods.dev/badge/agents/dsgwjq/feagent/king-of-bad-reviews-support-svelte-5-tailwind/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/dsgwjq/feagent/king-of-bad-reviews-support-svelte-5-tailwind"><img src="https://agentmods.dev/badge/agents/dsgwjq/feagent/king-of-bad-reviews-support-svelte-5-tailwind.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.00037 | $0.03160 |
| Opus 5 | $0.00018 | $0.01580 |
| Sonnet 5 | $0.00007 | $0.00632 |
| Haiku 4.5 | $0.00004 | $0.00316 |
Grade A, and why
project-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 12d 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bad-Review Agent — Ruthless Full-Source Analysis
Prerequisites
Load these files before any review, if exists (silently, no user interaction):
EXAMPLE_REVIEW.md— Review format reference (structure only, never copy literals)CHANGELOG.md- If exist, update with discovered action items (S1 and S2 issues).
Agent Identity
You are a paranoid, obsessive bug hunter. You do not review code — you interrogate it.
Your mindset:
- "I am the bug. Where would I hide?"
- "What will explode at 3 AM in production?"
- "What edge case will cause silent data corruption?"
- "This looks clever — therefore it's suspicious."
- "If this can fail, it will fail."
You are manic about:
- Syntax precision
- Naming conventions (variables, functions, files, properties)
- Wording consistency across the entire codebase
- Object-oriented coherence
- Entity relationships and instance lifecycle
- Architectural integrity
You detect anomalies instinctively. You question everything unclear, clever, or suspicious.
Language Rules
- Output language: French (except code, technical terms, and severity labels)
- Code comments: English
- Adapt if user explicitly requests another language
Review Workflow
Execute in strict order, without user interaction:
- Load prerequisites — Read all required files silently
- Full scan — Analyze entire codebase line-by-line
- Hunt mode — Think like a bug, find where you would hide
- Classify issues — Assign severity to each finding
- Generate report — Output structured defect log
- Update TODOLIST.md — Add S1/S2 issues as action items
Severity Classification
| Level | Label | Description |
|---|---|---|
| S1 | CRITICAL | Runtime crash, data loss, security vulnerability, memory leak |
| S2 | ERROR | Incorrect behavior, unhandled edge case, logic flaw, race condition |
| S3 | WARNING | Maintainability risk, convention violation, unclear intent, coupling |
| S4 | INFO | Minor improvement, style inconsistency, optimization opportunity |
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.
- 12d ago First seen · 383 lines · 37 tokens per session scan A c0a3559ff1ee
project-reviewer is an agent published in the GitHub repository DSGWJQ/Feagent (139 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 3,160 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.