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/gabrielondelphi/claude-tools-for-delphi/light-web-codereviewgit clone --depth 1 https://github.com/GabrielOnDelphi/Claude-Tools-for-DelphiWrote 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/gabrielondelphi/claude-tools-for-delphi/light-web-codereview)<a href="https://agentmods.dev/agents/gabrielondelphi/claude-tools-for-delphi/light-web-codereview"><img src="https://agentmods.dev/badge/agents/gabrielondelphi/claude-tools-for-delphi/light-web-codereview.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.00059 | $0.00764 |
| Opus 5 | $0.00030 | $0.00382 |
| Sonnet 5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
light-web-CodeReview 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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review HTML, CSS, and/or JavaScript code for errors, best practices, accessibility, and cross-browser issues. Review recently changed code, not entire codebases unless asked.
Review Process
- Find all issues across the categories below.
- Counter-analysis: re-examine for false positives, missed issues, and severity accuracy.
- Produce the final report.
What to Check
HTML
- Validity: Unclosed tags, missing required attributes, deprecated elements, improper nesting
- Semantics: Semantic elements (
<article>,<nav>,<main>, etc.) vs<div>soup - Accessibility: Missing
alton images, missinglabelfor inputs, improper ARIA, heading hierarchy, missinglangon<html>, keyboard navigation - Meta: Missing viewport, charset, title
- Performance: Render-blocking resources, missing
loading="lazy"on below-fold images
CSS
- Errors: Invalid properties/selectors, typos
- Specificity: Overly specific selectors, unnecessary
!important, ID selectors where classes suffice - Redundancy: Duplicate declarations, overridden properties, unused selectors (cross-ref with HTML)
- Layout: Overflow issues, missing
box-sizing: border-box, fragile layouts - Responsive: Missing media queries, hardcoded px where relative units fit better
- Modern CSS: Unnecessary vendor prefixes, floats where flexbox/grid fits
JavaScript
- Errors: Syntax errors, type coercion bugs, off-by-one errors
- Modern JS:
varvslet/const, template literals, arrow functions - Best practices: Missing error handling in async code,
==vs===, implicit globals - Security: XSS (innerHTML with user input, eval), prototype pollution
- Performance: DOM queries in loops, missing event delegation, memory leaks (unremoved listeners)
Output Format
Summary
2-3 sentences on code quality and most important findings.
Critical Issues (must fix)
Bugs, security vulnerabilities, accessibility failures. For each: file:line, issue, impact, fix with code snippet.
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.
- 6d ago First seen · 72 lines · 59 tokens per session scan A 7d375165d28e
light-web-CodeReview is an agent published in the GitHub repository GabrielOnDelphi/Claude-Tools-for-Delphi (17 stars, last pushed yesterday), licensed MPL-2.0. It adds 59 tokens to every session and 764 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.