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 commands/adrianosantostreina/delphi-dev/new-projectgit 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/commands/adrianosantostreina/delphi-dev/new-project)<a href="https://agentmods.dev/commands/adrianosantostreina/delphi-dev/new-project"><img src="https://agentmods.dev/badge/commands/adrianosantostreina/delphi-dev/new-project.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.1 | $0.00017 | $0.02680 |
| Opus 5 | $0.00009 | $0.01340 |
| Sonnet 5 | $0.00003 | $0.00536 |
| Haiku 4.5 | $0.00002 | $0.00268 |
Grade A, and why
new-project 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crie a estrutura inicial de um novo projeto Delphi seguindo boas práticas de arquitetura.
Idioma de saída: Detecte o idioma da primeira mensagem do usuário e conduza o levantamento e as explicações nesse idioma. Padrão: pt-BR. Suportados: pt-BR, en-US. Honre overrides: "respond in English" / "responda em português". Nomes de pastas e arquivos do scaffold seguem a convenção e não são traduzidos.
Passo 1 — Levantar requisitos
Pergunte ao usuário:
- Nome do sistema/projeto?
- Tipo: VCL / FMX / REST API / Library?
- Banco de dados? Componente de acesso?
- Arquitetura desejada: simples (Form + DataModule) / camadas (Model, Service, Repository)?
- Frameworks de terceiros? (ACBr, Horse, FastReport, etc.)
Passo 2 — Propor estrutura de pastas
Exemplo para projeto em camadas:
NomeProjeto/
├── src/
│ ├── model/ # entidades e DTOs
│ ├── interfaces/ # contratos (IService, IRepository)
│ ├── service/ # regras de negócio
│ ├── repository/ # acesso a dados
│ ├── presentation/ # forms e frames
│ └── shared/ # utilitários, constantes, exceções
├── tests/ # DUnitX
├── docs/
└── NomeProjeto.dproj
Passo 3 — Gerar arquivos base
Gerar também o
.dproj(o arquivo MSBuild — sem ele não há build) comProjectGuidhexadecimal válido, as plataformas escolhidas no Passo 1 eDCC_UnitSearchPathcobrindo as pastas desrc/. Conferir os tipos das propriedades na seção "Armadilhas conhecidas" abaixo antes de escrever — valor de tipo errado quebra o build com mensagem sem relação com a causa.
Crie os arquivos iniciais:
NomeProjeto.dpr— project file limpo- Unit de exceções customizadas do domínio
- Interface base de repositório (ICRUDRepository)
- DataModule de conexão (se aplicável)
- Form principal com nomenclatura correta
Aplique todos os padrões do Delphi Style Guide em cada arquivo gerado.
Fluxo adicional para projeto FMX
Quando o usuário escolher FMX no Passo 1, faça estas perguntas extras antes de gerar:
- Plataformas alvo: Windows / Android / iOS / macOS / Linux? (múltipla escolha)
- Se Android ou iOS selecionado:
- Orientação: Portrait / Landscape / Both?
- Banco de dados local: SQLite via FireDAC? (s/n)
- Permissões necessárias: câmera / GPS / storage / contatos? (múltipla escolha)
- Push notifications FCM/APNS? (s/n)
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 · +131 lines 9f4838b38439
- 6d ago First seen · 91 lines · 17 tokens per session scan A e62b486da591
new-project is a command published in the GitHub repository adrianosantostreina/delphi-dev (79 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 2,680 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.