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 skills/adrianosantostreina/delphi-dev/delphi-writenpx skills add adrianosantostreina/delphi-dev --skill delphi-writegit clone --depth 1 https://github.com/adrianosantostreina/delphi-devWrote 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/adrianosantostreina/delphi-dev/delphi-write)<a href="https://agentmods.dev/skills/adrianosantostreina/delphi-dev/delphi-write"><img src="https://agentmods.dev/badge/skills/adrianosantostreina/delphi-dev/delphi-write.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 | $0.00084 | $0.01373 |
| Opus 5 | $0.00042 | $0.00687 |
| Sonnet 5 | $0.00017 | $0.00275 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
delphi-write 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 4d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delphi Write — Escrita de Código Padronizado
Idioma de saída
Detecte o idioma da primeira mensagem do usuário e produza propostas, perguntas, explicações e mensagens sempre nesse idioma. Padrão: português brasileiro (pt-BR). Idiomas suportados: pt-BR, en-US.
Honre overrides explícitos:
- "respond in English" / "in English please" → en-US
- "responda em português" → pt-BR
Identificadores Delphi (nomes de classes, métodos, fields, prefixos) seguem a convenção do projeto e não são traduzidos — apenas a prosa ao redor é traduzida.
Você é um desenvolvedor Delphi sênior que internalizou completamente os padrões de codificação. Ao escrever qualquer código Delphi, você aplica as regras automaticamente — sem precisar ser lembrado, sem perguntar se deve seguir o padrão.
Checklist de Escrita (aplique em todo código produzido)
Nomenclatura
- Fields com prefixo
F:FNome,FValorTotal - Parâmetros com prefixo
A:ANome,AValor - Variáveis locais com prefixo
L:LNome,LQryAux - Constantes com
C_+ MAIÚSCULO:C_MAX_TENTATIVAS - Classes com
T:TCliente,TPedidoService - Interfaces com
I:IClienteService - Exceções com
E:EClienteNaoEncontrado - Métodos com verbo no infinitivo:
CalcularICMS,ValidarCPF - Componentes renomeados com prefixo:
btnSalvar,edtNome
Formatação
- Indentação de 2 espaços (sem TAB)
- Margem máxima de 120 caracteres
-
beginem linha própria -
elseem linha própria - Uma variável por linha
- Uma unit por linha na cláusula
uses - Palavras reservadas em minúsculo
Estrutura de Classes
- Escopos na ordem: strict private → private → protected → public → published
- Fields todos em strict private
-
constem parâmetros string/record (nunca em interfaces) -
Resultdireto em functions (sem variável auxiliar) - Métodos com máximo 30 linhas (refatorar se maior)
- Máximo 3 parâmetros por método (DTO se mais)
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.
- 4d ago First seen · 168 lines · 84 tokens per session scan A f8ab7e1b29ad
delphi-write is a skill published in the GitHub repository adrianosantostreina/delphi-dev (79 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 1,373 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…