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-CheckOsCompatibility/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-checkoscompatibility)<a href="https://agentmods.dev/skills/gabrielondelphi/claude-tools-for-delphi/light-code-checkoscompatibility"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-code-checkoscompatibility/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-checkoscompatibility"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-code-checkoscompatibility.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.00061 | $0.00714 |
| Opus 5.5 | $0.00024 | $0.00286 |
| Sonnet 5.5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
light-code-CheckOsCompatibility 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/light-code-CheckOsCompatibility — Cross-Platform Compatibility Audit
This is a thin launcher. Your only job is to resolve the input scope and launch the
light-code-CheckOsCompatibility agent. You do NOT audit the code yourself.
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 audit 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 audit all or narrow the scope. - No argument → audit the
.pasfiles with uncommitted changes. Rungit status --porcelainand keep the.pasfiles it lists (modified, added, or renamed) — this is "the code I just changed". If that list is empty, ask the user which file or folder to audit. Do NOT default to the whole repository.
If the user names a target platform (Android, iOS, macOS, Linux), carry that into the agent's prompt so it focuses there. Print the resolved audit set as a short list before launching.
Step 2 — Launch the agent
Call the Agent tool with subagent_type: "light-code-CheckOsCompatibility". Pass it the full audit set
in one prompt, plus any target platform the user mentioned. The agent reads the project
CLAUDE.md for the declared target platforms and intentional platform-specific code, scans the
files, and reports issues (Windows-only units/APIs, hardcoded paths, missing {$IFDEF} guards,
mobile-incompatible patterns).
Relay its final report to the user.
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 audited, how many issues by severity, and which need a human decision.
Rules
- You do not audit code. Resolving the scope, launching the agent, and summarizing is your entire job. The agent does the audit.
- This agent only reports (its tools are read + web). It does not apply fixes — so do not promise fixes; relay the findings and let the user decide.
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 89cfaaceab62
- 2mo ago First seen · 55 lines · 61 tokens per session scan A c14847f44c39
light-code-CheckOsCompatibility 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 61 tokens to every session and 714 once invoked, about $0.0002 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
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…