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-new-Feature/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-new-feature)<a href="https://agentmods.dev/skills/gabrielondelphi/claude-tools-for-delphi/light-new-feature"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-new-feature/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-new-feature"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-new-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 53 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Excessive Agency · line 70 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00083 | $0.05733 |
| Opus 5 | $0.00042 | $0.02867 |
| Sonnet 5 | $0.00017 | $0.01147 |
| Haiku 4.5 | $0.00008 | $0.00573 |
Grade A, and why
light-new-Feature 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 5d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delphi New Feature — Pipeline Orchestrator
This skill takes a feature from a one-line brief to a working, tested vertical slice.
You (the main thread) are the orchestrator. Most of the heavy lifting you do yourself
(the design interview, the PRD, the slicing), but you launch sub-agents for the two jobs that
must run in isolation: compiling (the light-compiler agent) and the final verification
(light-review-PostEdit, optionally light-review-Full). You never hand-run a build script.
It is the front-half mirror of light-review-Full: light-review-Full covers review → verify → fix → doc;
this skill covers align → PRD → slice → implement, then chains into those review skills.
Reuse LightSaber first — do not reinvent it
LightSaber exists to eliminate boilerplate. Before writing any new unit, class, or utility, assume
LightSaber already does it — and check. Hand-rolling something it provides is the most common avoidable
mistake here: untested code, drift from the user's conventions, a skipped mature implementation. When
you do reuse, uses the LightSaber unit rather than copying its code; when nothing fits, write new
code but say so explicitly ("no LightSaber unit covers X, so I am adding it").
Where to look (naming is Light<Framework>.<Layer>.<Feature>):
| Need | Look in |
|---|---|
| Strings, dates, files, streams, binary, INI, encoding, logging — platform-agnostic | LightCore.* — e.g. LightCore.pas (200+ string/date/form helpers), LightCore.IO.pas (files/folders/disks), LightCore.StreamBuff.pas (typed binary stream, drop-in TFileStream replacement), LightCore.Binary.pas, LightCore.INIFile.pas, LightCore.AppData.pas |
| Windows utilities — registry, shell, dialogs, system info, clipboard | LightVcl.Common.* |
| Downloads, email, HTML | LightVcl.Internet.* |
| Image processing, GDI, effects | LightVcl.Graphics.* |
| Visual VCL controls (80+: TrayIcon, StringGrid, spin edits, …) | LightVcl.Visual.* |
| FMX utilities / visual controls | LightFmx.Common.* / LightFmx.Visual.* |
| App lifecycle, GUI auto-save/restore, settings, single-instance, updater, uninstaller, EULA, translation | AppData (3-layer: TAppDataCore → TAppData → TLightForm), SaveForm/LoadForm, the Updater\, AutoTranslator\ units |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +1 lines 7c13c796d90a
- 7d ago Changed · +10 lines 540af3baf642
- 11d ago First seen · 346 lines · 83 tokens per session scan A 6613a69e9266
light-new-Feature is a skill published in the GitHub repository GabrielOnDelphi/Claude-Tools-for-Delphi (18 stars, last pushed 3d ago), licensed MPL-2.0. It adds 83 tokens to every session and 5,733 once invoked, about $0.0004 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 skills, from other repositories
typescript-test-writing
Use this skill when writing or modifying tests in the llxprt-code repository. Covers mandatory TDD, behavioral testing, bun:test conventions and file naming, mock hygiene (no mock theater), and what never to test. Distilled from dev-docs/RULES.md, which remains the source of truth.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-fsharp
F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
golang-testing
A guide to testing Go programs, including test-driven development (TDD), table-driven tests, coverage, and debugging. TDD means writing a failing test before implementing the code that makes it pass.