altimate-code: Skill for OpenCode

.opencode/skills/query-optimize/SKILL.md

query-optimize is a skill for OpenCode from AltimateAI/altimate-code. It costs 12 tokens per session (924 once invoked), scanned A, original, MIT.

A read-only SQL reviewer that examines a query for performance problems and suggests rewritten SQL. SQL is the language used to retrieve and transform data in databases.

In plain words
What is it for?
Use it to optimize SQL for databases such as Snowflake, PostgreSQL, BigQuery, or DuckDB, using table information when a warehouse connection is available.
Why use it?
It helps identify slow or inefficient queries and can verify that proposed rewrites return the same results as the original.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

This is AltimateAI/altimate-code's own configuration. It tells OpenCode how to work on altimate-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything altimate-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AltimateAI/altimate-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AltimateAI/altimate-code/main/.opencode/skills/query-optimize/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/AltimateAI/altimate-code

Made for: OpenCode.

Wrote 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.

agentmods badge for query-optimize

README.md
[![agentmods](https://agentmods.dev/badge/skills/altimateai/altimate-code/query-optimize/github.svg)](https://agentmods.dev/skills/altimateai/altimate-code/query-optimize)
Your own site
<a href="https://agentmods.dev/skills/altimateai/altimate-code/query-optimize"><img src="https://agentmods.dev/badge/skills/altimateai/altimate-code/query-optimize/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for query-optimize

Your own site · 80×15
<a href="https://agentmods.dev/skills/altimateai/altimate-code/query-optimize"><img src="https://agentmods.dev/badge/skills/altimateai/altimate-code/query-optimize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 924 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00924
Opus 5.5 $0.00005 $0.00370
Sonnet 5.5 $0.00002 $0.00185
Haiku 4.5 $0.00001 $0.00092

Measured 1mo ago against content hash 643cd0ec1391, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

query-optimize 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 1mo 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.

.opencode/skills/query-optimize/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Query Optimize

Requirements

Agent: any (read-only analysis) Tools used: altimate_core_rewrite (with verify_equivalence: true), sql_analyze, sql_explain, read, glob, schema_inspect, warehouse_list

Analyze SQL queries for performance issues and suggest concrete optimizations including rewritten SQL.

Workflow

  1. Get the SQL query -- Either:

    • Read SQL from a file path provided by the user
    • Accept SQL directly from the conversation
    • Read from clipboard or stdin if mentioned
  2. Determine the dialect -- Default to snowflake. If the user specifies a dialect (postgres, bigquery, duckdb, etc.), use that instead. Check the project for warehouse connections using warehouse_list if unsure.

  3. Run the verified optimizer:

    • If the user has a warehouse connection, first call schema_inspect on the relevant tables to build schema context (needed both for better rewrites — e.g. SELECT * expansion — and to verify equivalence)
    • Call altimate_core_rewrite with the SQL, schema context, and verify_equivalence: true. This proposes rewrites AND proves each one returns the same results as the original in a single step. The result is partitioned into verified-equivalent rewrites (safe to apply) and unverified rewrites (review before applying), so you never recommend a rewrite that silently changes semantics.
  4. Run detailed analysis:

    • Call sql_analyze with the same SQL and dialect to get the full anti-pattern breakdown with recommendations
  5. Get execution plan (if warehouse connected):

    • Call sql_explain to run EXPLAIN on the query and get the execution plan
    • Look for: full table scans, sort operations on large datasets, inefficient join strategies, missing partition pruning
    • Include key findings in the report under "Execution Plan Insights"
  6. Equivalence verification is built into step 3 (verify_equivalence: true):

    • Present the verified-equivalent rewrites as safe to apply.
    • Present unverified rewrites separately with their reason ("review before applying") — do not recommend applying these without manual review.
    • If no schema was available, all rewrites come back unverified; say so and recommend supplying a schema (or a warehouse connection) to enable verification.

Read the full file on GitHub · 87 lines

Changes

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.

  1. 1mo ago First seen · 87 lines · 12 tokens per session scan A 643cd0ec1391

Subscribe to this mod's changes

query-optimize is a skill published in the GitHub repository AltimateAI/altimate-code (813 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 924 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other skills, from other repositories

zarr-python

Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.

synthetic-sciences/openscience · 42 tokens

benchling-integration

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

synthetic-sciences/openscience · 44 tokens

aeon

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard…

synthetic-sciences/openscience · 74 tokens

geopandas

Python library for working with geospatial vector data including shapefiles, GeoJSON, and GeoPackage files. Use when working with geographic data for spatial analysis, geometric operations, coordinate transformations, spatial joins, overlay operations, choropleth mapping, or any task involving…

synthetic-sciences/openscience · 125 tokens

hdf5-pde-data-loading

Patterns for loading PDE simulation datasets (PDEBench, PhiFlow, JAX-CFD) from HDF5 files. Handles layout detection (single tensor vs separate variables), spatial/temporal downsampling, multi-variable systems, HuggingFace and DaRUS data sources, and efficient PyTorch DataLoader creation. Use when preparing PDE data…

synthetic-sciences/openscience · 82 tokens

ontology-database

Typed knowledge graph via TSV append-only log — entity CRUD, directed relations, schema validation, multi-hop reasoning. CLI via x ondb, protocol readable by AWK/Python/JS/SQLite.

x-cmd/x-cmd · 45 tokens