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/celigo/ai/writing-sqlnpx skills add celigo/ai --skill writing-sqlgit clone --depth 1 https://github.com/celigo/aiWhat 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.00070 | $0.05605 |
| Opus 5 | $0.00035 | $0.02802 |
| Sonnet 5 | $0.00014 | $0.01121 |
| Haiku 4.5 | $0.00007 | $0.00560 |
Grade A, and why
writing-sql 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing SQL for RDBMS Integrations
RDBMS exports and imports use SQL queries to read from and write to relational databases. Queries are Handlebars templates -- the platform evaluates expressions like {{{record.fieldName}}} at runtime, then executes the resulting SQL against the connected database.
This skill covers what SQL to write and how to write it. For which adaptor type to use, connection setup, and queryType selection, see the related skills below.
Quick Reference
Context decision matrix
| Where | Field | Handlebars prefix | Braces | Example |
|---|---|---|---|---|
| Export query | rdbms.query |
record. (parameterized) or none (standalone) |
{{{ }}} |
SELECT * FROM orders WHERE id = {{{record.id}}} |
| Export delta query | rdbms.query |
platform-injected tokens | {{ }} or {{{ }}} |
WHERE updated_at > '{{lastExportDateTime}}' |
| Export once mark-as-processed | rdbms.once.query |
record. |
{{{ }}} |
UPDATE orders SET exported = true WHERE id = {{{record.id}}} |
| Import per_record query | rdbms.query[] |
record. |
{{{ }}} |
INSERT INTO users (name) VALUES ('{{{record.name}}}') |
| Import per_page query | rdbms.query[] |
batch_of_records + record. |
{{{ }}} |
{{#each batch_of_records}}...{{{record.field}}}...{{/each}} |
| Import bulk_load override | rdbms.bulkLoad.overrideMergeQuery |
staging table ref | {{ }} |
MERGE INTO target USING {{import.rdbms.bulkLoad.preMergeTemporaryTable}} |
Key syntax rules
- Always use
record.prefix (AFE 2.0). Never barefieldNameordata.fieldName. - Prefer triple braces
{{{ }}}for values in SQL. Double braces{{ }}auto-wrap values in single quotes in RDBMS context -- this silently corrupts numeric values and breaks SQL syntax. - Add your own quotes for strings:
'{{{record.name}}}'. Triple braces give you full control. - No quotes for numbers:
{{{record.quantity}}}. - Import
queryis an array of strings, not a single string:["INSERT INTO ..."]. - Nested fields use dot notation:
{{{record.address.city}}}.
What ships with it
2 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 · 537 lines · 70 tokens per session scan A 7522ce3376aa
writing-sql is a skill published in the GitHub repository celigo/ai (3 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 5,605 once invoked, about $0.0003 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
prepare-mcp-integration
Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection. Use for new integration research and delivery; not for ad hoc connector coding that bypasses the playbooks.
webhook-subscriptions
Webhook subscriptions: event-driven agent runs.
agent-builder
Use when creating, improving, or troubleshooting Claude Code subagents. Expert guidance on agent design, system prompts, tool access, model selection, and best practices for building specialized AI assistants.
creating-skills
Use when creating new agent skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, discovery optimization, and real examples.
running-and-testing-locally
Use when running the Nango application locally for development and browser testing - covers Docker services, dev commands, service URLs, and troubleshooting startup issues.
creating-integration-docs
Use when adding or editing Nango integration documentation - creates and maintains integration pages, setup guides, connect guides, navigation, and provider metadata following established patterns.