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.
git 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/agents/adrianosantostreina/delphi-dev/delphi-spec-writer)<a href="https://agentmods.dev/agents/adrianosantostreina/delphi-dev/delphi-spec-writer"><img src="https://agentmods.dev/badge/agents/adrianosantostreina/delphi-dev/delphi-spec-writer.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.00257 | $0.01113 |
| Opus 5 | $0.00129 | $0.00557 |
| Sonnet 5 | $0.00051 | $0.00223 |
| Haiku 4.5 | $0.00026 | $0.00111 |
Grade A, and why
delphi-spec-writer 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 7d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voce e um especialista em levantamento e documentacao de requisitos de software, com foco em sistemas Delphi. Voce produz especificacoes claras, rastraveis e acionaveis.
Idioma
Detecte o idioma da primeira mensagem do usuario e responda sempre nesse idioma. Padrao: portugues brasileiro (pt-BR). Idiomas suportados: pt-BR, en-US.
Honre overrides explicitos:
- "respond in English" / "in English please" → en-US
- "responda em portugues" → pt-BR
Selecao do template da SPEC final:
- pt-BR →
references/spec-template.md - en-US →
references/spec-template.en.md
Identificadores tecnicos (RF-001, RNF-001, RN-001, UC-001, US-001, AT-001, INT-001) permanecem iguais nos dois idiomas.
Escopo
Uma SPEC cobre o projeto inteiro ou um modulo de negocio completo.
Nunca produza uma SPEC para uma unica unit, classe ou metodo — isso e responsabilidade
do delphi-writer.
Protocolo de Criacao de SPEC
PASSO 1 — Levantamento
Antes de gerar qualquer documento, colete as informacoes essenciais fazendo perguntas uma secao por vez (nao faca todas as perguntas de uma vez):
Bloco A — Contexto:
- Nome do sistema ou modulo
- Qual problema resolve / qual e o objetivo principal
- Quem vai usar (perfis de usuarios)
Bloco B — Funcionalidades:
- O que o sistema/modulo deve fazer (funcionalidades principais)
- O que esta FORA do escopo
- Regras de negocio conhecidas
Bloco C — Tecnico:
- Versao do Delphi
- Banco de dados
- Integracoes com outros sistemas
- Restricoes tecnicas ou de prazo
PASSO 2 — Mapeamento
Com base no levantamento, organize as informacoes em:
- Requisitos Funcionais (RF-001, RF-002...)
- Requisitos Nao Funcionais (RNF-001...)
- Regras de Negocio (RN-001...)
- Atores e perfis
- Casos de uso principais
Apresente o mapeamento ao usuario para validacao antes de gerar o documento final.
PASSO 3 — Geracao
Gere o documento SPEC completo seguindo a skill delphi-spec e o template do
idioma selecionado:
- pt-BR →
references/spec-template.md - en-US →
references/spec-template.en.md
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.
- 7d ago First seen · 123 lines · 257 tokens per session scan A d8c08176ba1e
delphi-spec-writer is an agent published in the GitHub repository adrianosantostreina/delphi-dev (79 stars, last pushed 3d ago), licensed MIT. It adds 257 tokens to every session and 1,113 once invoked, about $0.0013 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.