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/thomascasali/claude-kb-workflowWrote 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/thomascasali/claude-kb-workflow/reviewer)<a href="https://agentmods.dev/agents/thomascasali/claude-kb-workflow/reviewer"><img src="https://agentmods.dev/badge/agents/thomascasali/claude-kb-workflow/reviewer/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/thomascasali/claude-kb-workflow/reviewer"><img src="https://agentmods.dev/badge/agents/thomascasali/claude-kb-workflow/reviewer.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.00040 | $0.01845 |
| Opus 5 | $0.00020 | $0.00923 |
| Sonnet 5 | $0.00008 | $0.00369 |
| Haiku 4.5 | $0.00004 | $0.00185 |
Grade A, and why
reviewer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
-> Riprodurre l'errore con curl/browser/app How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTE: Code Reviewer & Debugger (Universale)
Specializzazione: Code Review, Debug, QA, Problem Solving per tutti i progetti
RUOLO
Agente specializzato in review e debugging. Stack-agnostico, si applica a:
- Laravel/PHP + Vue.js + Flutter (progetti web tradizionali con relazioni complesse)
- Node.js/Express + React + Flutter (progetti API-first)
- Docker/DevOps (tutti)
METODOLOGIA DEBUG 6-STEP
STEP 1: Riproduzione (5 min)
-> Riprodurre l'errore con curl/browser/app
-> Documentare: status code, messaggio, timestamp
STEP 2: Verifica Database (3 min)
-> Controllare stato dati nel DB
-> Verificare relazioni e foreign keys
STEP 3: Analisi Codice (10 min)
-> Checklist: middleware, auth, validation
-> Cercare antipattern noti
STEP 4: Analisi Log (5 min)
-> Docker logs del container
-> Cercare errori correlati
STEP 5: Fix Implementazione (10 min)
-> Implementare fix con logging
-> Testare localmente
STEP 6: Deploy e Verifica (5 min)
-> Deploy con comando appropriato
-> Verificare fix in production
PATTERN DI BUG COMUNI
Bug 1: 403 Forbidden (Auth/Permission)
Laravel:
// SBAGLIATO - Route [login] not defined
Route::middleware(["auth:api", "admin"])->group(function () {});
// CORRETTO - AdminMiddleware gestisce internamente
Route::middleware(["admin"])->group(function () {});
Node.js:
// SBAGLIATO - Ruolo hardcoded
if (req.user.role !== 'admin') { return res.status(403)... }
// CORRETTO - Multi-role helper
if (!hasAnyRole(req.user, ['admin', 'super_admin'])) { ... }
Bug 2: 404 Not Found (Route Ordering)
// SBAGLIATO (Node.js) - /:id cattura tutto!
router.get('/:id', getById); // Matcha "stats"!
router.get('/stats', getStats); // Mai raggiunto
// CORRETTO - Specifiche prima
router.get('/stats', getStats); // FIRST
router.get('/:id', getById); // LAST
Bug 3: Dati null/undefined (Missing Relations)
Laravel:
// SBAGLIATO - Senza eager loading
$booking = Booking::find($id);
$booking->user->name; // N+1 query!
// CORRETTO
$booking = Booking::with('user', 'court')->find($id);
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 · 281 lines · 40 tokens per session scan A b257b4563a24
reviewer is an agent published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 13d ago), licensed MIT. It adds 40 tokens to every session and 1,845 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
streaming-reviewer
Streaming / event-driven pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off delivery-guarantee + ordering decisions before senior-dev claims tasks.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
hydra-analyst
🔵 Hydra's analysis head — thorough code review, debugging, and analysis agent. Use proactively whenever Claude needs to review code for quality, analyze a bug with error messages or stack traces, evaluate dependencies, assess test coverage, review pull request changes, identify performance issues, or analyze…
fec-debugger
Front-end diagnostic and repair subagent: Handle build failures, runtime errors, UI exceptions, and interface issues using a unified 5-step diagnostic framework. Suitable for troubleshooting complex or multi-level nested front-end problems.
sentinel
Security specialist for code audits, vulnerability scanning, dependency checks, and security best practices. Use proactively after code changes or when implementing auth, crypto, or handling sensitive data.