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/celigo/ai/celigo-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.00039 | $0.00230 |
| Opus 5 | $0.00019 | $0.00115 |
| Sonnet 5 | $0.00008 | $0.00046 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
celigo-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.
What it actually says
Help me write SQL for a Celigo RDBMS export or import. Use the writing-sql skill for dialect differences, MERGE/upsert patterns, and bulk operations, and the writing-handlebars skill for the {{{record.field}}} templating that embeds record values.
Steps:
- Ask which database/dialect (Snowflake, SQL Server, Postgres, MySQL, Oracle, BigQuery, etc.) and whether this is an export (read) or import (write).
- Ask for the table/columns and the operation (select, insert, update, upsert/MERGE, delete).
- Produce the query using triple braces
{{{record.field}}}for values (never double braces, which wrap in single quotes), noting where literal quotes are needed. - Call out dialect-specific syntax and any parameterization or bulk considerations.
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 · 13 lines · 39 tokens per session scan A 53adf7b2bedc
celigo-sql is a command published in the GitHub repository celigo/ai (3 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 230 once invoked, about $0.0002 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 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.