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/secondlifes/delphi-expert/firebird-databasenpx skills add SecondLifes/delphi-expert --skill firebird-databasegit clone --depth 1 https://github.com/SecondLifes/delphi-expertWhat 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.00025 | $0.00516 |
| Opus 5 | $0.00013 | $0.00258 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
firebird-database 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firebird Database — Skill
Use this skill when working with Firebird database in Delphi projects via FireDAC.
When to Use
- When configuring FireDAC connection with Firebird
- When creating tables, generators, stored procedures, triggers, domains and views
- When implementing Repositories with FireDAC + Firebird
- When working with transactions, isolation levels and concurrency
- When planning schema migrations (versioned scripts)
- When optimizing queries and indexes for Firebird
Quick Reference
Minimum connection:
FConnection.DriverName := 'FB';
FConnection.Params.Values['CharacterSet'] := 'UTF8'; //ALWAYS UTF8
FConnection.Params.Values['SQLDialect'] := '3'; //NEVER Dialect 1
FConnection.Params.Values['Protocol'] := 'TCPIP'; //Or 'Local' for embedded
FConnection.Params.Values['PageSize'] := '16384'; // 16KB recomendado
FConnection.TxOptions.Isolation := xiReadCommitted; //Standard isolation
Golden rules: Dialect 3 always (never 1), RETURNING always needs Open (never ExecSQL), CharacterSet UTF8 always, parameterized queries only, CREATE TABLE IF NOT EXISTS does not exist (check RDB$RELATIONS instead). Full details and code for each are in the reference files below — read the one that matches the task at hand rather than guessing.
references/
Read only the file(s) relevant to the current task — this skill file is intentionally short; the depth lives in these files.
connection-and-types.md— supported versions, FireDAC connection setup (driver link, pooling), dialect 1 vs 3, Firebird ↔ Delphi data type mapping.schema-and-migrations.md— generators/sequences,IDENTITYcolumns,RETURNINGin Delphi, domains, triggers, migration scripts, runtime schema-existence checks, andgbakbackup/restore.querying.md— selectable vs executable stored procedures,EXECUTE BLOCK, and Packages (Firebird 3+).transactions-and-ops.md— transactions/isolation levels, event alerter (POST_EVENT), anti-patterns, Firebird Embedded integration testing, and the pre-flight checklist.
What ships with it
4 files 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.
- 2d ago First seen · 42 lines · 25 tokens per session scan A 92392b40a1de
firebird-database is a skill published in the GitHub repository SecondLifes/delphi-expert (3 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 516 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-31.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.