Borrowing it
Nothing to install: this file belongs to GabrielOnDelphi/Claude-Tools-for-Delphi. 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/GabrielOnDelphi/Claude-Tools-for-Delphi/main/.claude/skills/light-code-StyleChecker/SKILL.mdgit 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/skills/gabrielondelphi/claude-tools-for-delphi/light-code-stylechecker)<a href="https://agentmods.dev/skills/gabrielondelphi/claude-tools-for-delphi/light-code-stylechecker"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-code-stylechecker/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/skills/gabrielondelphi/claude-tools-for-delphi/light-code-stylechecker"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-code-stylechecker.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.00065 | $0.00797 |
| Opus 5.5 | $0.00026 | $0.00319 |
| Sonnet 5.5 | $0.00013 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
light-code-StyleChecker 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/light-code-StyleChecker — 3rd-party Code Style Audit
This is a thin launcher. Your only job is to resolve the input scope and launch the
light-code-StyleChecker agent. You do NOT review code yourself.
Scope reminder: this skill is for IMPORTED / 3RD-PARTY Delphi code only. For our own
project code, the right tool is /light-review-Full (deeper, real correctness review). If the user
points this at our own code, say so and suggest /light-review-Full — then proceed only if they
confirm.
Step 1 — Resolve the input
The argument is in $args. The user may pass a single .pas file, a folder, or several files.
Build the scan set:
- One or more explicit file paths → use them as-is.
- A folder → Glob
<folder>/**/*.pasfor the file list. If the result is large (more than ~25 files), tell the user the count and ask whether to scan all or narrow the scope. - No argument → ask the user which imported file or folder to scan. Do NOT default to the
whole repository, and do NOT fall back to
git status— 3rd-party code is usually already committed, so a git-diff scope would miss it.
Print the resolved scan set as a short list before launching, so the user can see the scope.
Step 2 — Launch the agent
Call the Agent tool with subagent_type: "light-code-StyleChecker". Pass it the full scan
set in one prompt. Tell it plainly that this is imported / 3rd-party code to audit for style
compliance, common mistakes, and dangerous patterns.
The agent reads the project CLAUDE.md for conventions, scans the files, reports findings, and
applies the safe fixes it is confident about. It also applies four mandatory reformatting passes
on imported code: a LightSaber-format unit header, Embarcadero keyword casing, if/then/else
layout, and no line wrapping. Relay its final report to the user — do not re-derive or
second-guess it.
Step 3 — Summary
Print a short summary (the agent's full report is already in the transcript — do not re-paste it): how many files scanned, how many issues found, how many fixed vs. flagged for a human decision.
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.
- 1mo ago Changed · +2 lines ee3e8a133f24
- 2mo ago First seen · 59 lines · 65 tokens per session scan A 38150e7f499d
light-code-StyleChecker is a skill published in the GitHub repository GabrielOnDelphi/Claude-Tools-for-Delphi (23 stars, last pushed 28d ago), licensed MPL-2.0. It adds 65 tokens to every session and 797 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…