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/altimateai/altimate-code/sql-translatenpx skills add AltimateAI/altimate-code --skill sql-translategit clone --depth 1 https://github.com/AltimateAI/altimate-codeWhat 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.00026 | $0.00644 |
| Opus 5 | $0.00013 | $0.00322 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
sql-translate 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Translate
Requirements
Agent: builder or migrator (may write translated SQL to files) Tools used: sql_translate, read, write, altimate_core_validate
Translate SQL queries from one database dialect to another using sqlglot's transpilation engine.
Workflow
-
Determine source and target dialects — If the user did not specify both dialects, ask which source and target dialects to use. Common dialects:
snowflake,bigquery,postgres,mysql,tsql,hive,spark,databricks,redshift,duckdb. -
Get the SQL to translate — Either:
- Read from a file path provided by the user (use
read) - Accept inline SQL from the user's message
- Read from clipboard or stdin if mentioned
- Read from a file path provided by the user (use
-
Call
sql_translatewith:sql: The SQL query textsource_dialect: The source dialecttarget_dialect: The target dialect
-
Review the result:
- If
successis true, present the translated SQL - If there are
warnings, explain each one and what may need manual adjustment - If
successis false, explain the error and suggest fixes
- If
-
Format the output showing:
- Original SQL (labeled with source dialect)
- Translated SQL (labeled with target dialect)
- Any warnings about lossy translations or features that need manual review
-
Offer next steps if applicable:
- Suggest running
altimate_core_validateon the translated SQL to verify syntax - Offer to write the translated SQL to a file
- Offer to translate additional queries
- Suggest running
Usage
The user invokes this skill with optional dialect and SQL arguments:
/sql-translate— Interactive: ask for source dialect, target dialect, and SQL/sql-translate snowflake postgres— Translate from Snowflake to PostgreSQL (will ask for SQL)/sql-translate snowflake postgres SELECT DATEADD(day, 7, CURRENT_TIMESTAMP())— Full inline translation
Supported Dialects
| Dialect | Key |
|---|---|
| Snowflake | snowflake |
| BigQuery | bigquery |
| PostgreSQL | postgres |
| MySQL | mysql |
| SQL Server | tsql |
| Hive | hive |
| Spark SQL | spark |
| Databricks | databricks |
| Redshift | redshift |
| DuckDB | duckdb |
| SQLite | sqlite |
| Oracle | oracle |
| Trino/Presto | trino / presto |
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 · 69 lines · 26 tokens per session scan A 842dcd5da127
sql-translate is a skill published in the GitHub repository AltimateAI/altimate-code (803 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 644 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 skills, from other repositories
technology-search
Search tech blogs, developer forums, and IT media (TechCrunch, Hacker News, 36氪, etc.) for software and hardware industry updates with heat ranking and EN↔CN translation. Use this skill only when the topic is clearly about programming, software, hardware, AI, or IT infrastructure.
email-draft
Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check.
omh-localization-review
This is a Hermes-native localization-review workflow skill.
store-listing-localizer
Automate Microsoft Store (Partner Center) listing localization for Intelligent Terminal (Store ID 9NMQC2SSJX24). Use when asked to export/import Store listings, localize release notes / descriptions / captions / features into 80+ languages, update listingData CSV, or push Store listing translations without manually…
text-tools
Text processing toolkit: translate, rewrite, regex, encoding/decoding, and formatting.
agentero-cli
Use the Agentero CLI (bin agentero) to create, discover, and inspect a local research vault and catalog—list/get papers, import by id/URL, check wikilinks, layout regions (figures/tables/formulas), write reading marks (highlight / 批注 / translate / ask), download assets, parse PAPER.md, export bib—without BYOA. Prefer…