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-md-DriftUpdate/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-md-driftupdate)<a href="https://agentmods.dev/skills/gabrielondelphi/claude-tools-for-delphi/light-md-driftupdate"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-md-driftupdate/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-md-driftupdate"><img src="https://agentmods.dev/badge/skills/gabrielondelphi/claude-tools-for-delphi/light-md-driftupdate.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.00150 | $0.00737 |
| Opus 5 | $0.00075 | $0.00368 |
| Sonnet 5 | $0.00030 | $0.00147 |
| Haiku 4.5 | $0.00015 | $0.00074 |
Grade A, and why
light-md-DriftUpdate 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 2d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update MD docs (launcher)
This skill is a thin launcher. The scan-verify-fix work is done by the light-md-DriftUpdate agent
in its own context window (reading every doc + grepping the code is heavy — keep it out of the main
context). Your job: decide whether to run, resolve the scope, launch the agent, relay its report.
Steps
-
Resolve scope (ask here if needed — the agent cannot). Glob
**/*.mdunder the project root, excludingnode_modules/,.git/,build/,Win32/,Win64/,__history/,*.dproj/,External/, vendored deps. If more than ~20 MD files match, ask the user which scope:- Root only (
CLAUDE.md,README.md) — the default if they don't care - Root +
docs/ - All
With
$argsnaming a file/glob, use that as the scope and skip the question. - Root only (
-
Launch the
light-md-DriftUpdateagent via the Agent tool withsubagent_type: light-md-DriftUpdate. Pass the resolved scope (the concrete file list or the chosen breadth) in the prompt. -
Print the agent's returned report verbatim. It lists BROKEN / STALE / NEW fixes it applied, plus any NEEDS CONFIRMATION items it left unapplied — surface those so the user can decide.
That's it. No scanning, no claim-verification, no edits in the skill itself — the agent does all of it and applies the surgical fixes.
Where the rules live (for the agent, not for you)
The agent loads the Delphi vocabulary + clarity references from
c:\Users\<you>\.claude\skills\light-md-DelphiIdiom\references\ so any new prose it writes is already
Delphi-idiomatic, and it holds the claim-extraction / verify / skip / anti-pattern rules. See
.claude/agents/light-md-DriftUpdate.md.
Claude Tools for Delphi — © 2026 Gabriel Moraru, gabrielmoraru.com — MPL-2.0
Autopilot for Delphi — Claude clicks, types and reads inside your running VCL / FMX app.
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.
- 2d ago Changed · -12 lines · +57 tokens per session d964b9999e3a
- 6d ago Changed · +2 lines d1841d81f64a
- 10d ago First seen · 56 lines · 93 tokens per session scan A ac61c6a2a62e
light-md-DriftUpdate is a skill published in the GitHub repository GabrielOnDelphi/Claude-Tools-for-Delphi (17 stars, last pushed 3d ago), licensed MPL-2.0. It adds 150 tokens to every session and 737 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…