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/ikarusmk/aicortex/sql-index-reviewnpx skills add IkarusMK/AIcortex --skill sql-index-reviewgit clone --depth 1 https://github.com/IkarusMK/AIcortexWhat 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.00032 | $0.00360 |
| Opus 5 | $0.00016 | $0.00180 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
sql-index-review 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 3d 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
SQL Index Review
When to use
A query is slow, or before shipping a query that runs hot.
Method
- Get the plan:
EXPLAIN (ANALYZE, BUFFERS)(Postgres) /EXPLAIN(MySQL). Look for Seq Scan / full table scan on big tables, and rows estimated ≫ rows returned. - Index what you filter, join, and sort on — columns in
WHERE,JOIN ... ON, andORDER BY. A composite index follows the column order of the predicate (equality columns first, then the range/sort column). - Covering index: include the selected columns so the index alone answers the
query (
INCLUDE (...)in Postgres) — no heap fetch. - Re-measure the plan after adding the index. Confirm the scan is now an index scan.
Don't
- Over-index: every index slows writes and costs storage. Drop unused ones.
- Index low-cardinality columns alone (e.g. a boolean) — rarely helps.
- Wrap an indexed column in a function in
WHERE(WHERE lower(email)=…) unless you built a matching expression index — it defeats the index.
Rule of thumb
Add the index that turns the most expensive Seq Scan in your hottest query into an index scan; verify with EXPLAIN before and after.
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.
- 3d ago First seen · 32 lines · 32 tokens per session scan A ae9aabc22294
sql-index-review is a skill published in the GitHub repository IkarusMK/AIcortex (9 stars, last pushed 14d ago), licensed Apache-2.0. It adds 32 tokens to every session and 360 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 skills, from other repositories
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…
malloy-gotchas-modeling
Common Malloy modeling mistakes and how to avoid them. Read BEFORE writing source definitions, dimensions, measures, or joins. Covers reserved words, NULL checks, date functions, type casts, field management (extend except/accept/rename vs include public/internal/private), and query-based source gotchas.
malloy-materialization
Add and debug Malloy Persistence materializations in a package - persist an expensive source so queries read a pre-built table. Read this whenever the user wants to materialize a source, add a persist annotation, speed up a slow source, or asks why a persist source isn't building.
malloy-materialization-tuning
Optimize a package's Malloy Persistence materializations for cost and performance using the malloy-pub CLI and the materialization history. Recommend what to persist, what to stop persisting, and how to schedule/scope it. Use when the user asks to make a package cheaper or faster, tune persistence, decide what to…
dataverse
Dataverse テーブル設計・構築・デモデータ投入・セキュリティロール作成。ソリューション作成からテーブル・リレーション・ローカライズ・権限設定まで Python スクリプトで一括構築する。.
database
Query and manage SQLite, PostgreSQL, and MySQL databases from the command line. Use when the user asks to run SQL queries, inspect database schemas, create or alter tables, import or export data, manage indexes, analyze query performance with EXPLAIN, back up or restore databases, or perform CRUD operations via…