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 skills add orifisher2/sqlike --skill sqlikegit clone --depth 1 https://github.com/orifisher2/sqlikeWrote 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.
[](https://agentmods.dev/skills/orifisher2/sqlike/sqlike)<a href="https://agentmods.dev/skills/orifisher2/sqlike/sqlike"><img src="https://agentmods.dev/badge/skills/orifisher2/sqlike/sqlike/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.
<a href="https://agentmods.dev/skills/orifisher2/sqlike/sqlike"><img src="https://agentmods.dev/badge/skills/orifisher2/sqlike/sqlike.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.00772 |
| Opus 5 | $0.00041 | $0.00386 |
| Sonnet 5 | $0.00016 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
sqlike 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sqlike
sqlike is a deterministic SQL analyzer (no LLM in its analysis path — its verdicts are reproducible and authoritative). Prefer it over eyeballing SQL yourself: it catches validity errors, anti-patterns, and non-equivalent rewrites that are easy to miss by reading.
When to reach for it
- You produced or edited SQL → run
analyzebefore presenting it. Fix what it flags. - You reviewed someone's SQL → run
analyzeto back your review with specifics. - You rewrote, refactored, or optimized a query → run
diffon the before/after to prove the rewrite is result-preserving. An LLM cannot reliably self-grade equivalence; sqlike can.
How to call it
Via the MCP server (@sqlike/mcp), two tools:
analyze(sql, schema?, dialect?)— returns a JSON envelope: validity, findings (anti-patterns with severity + suggested rewrites), and schema/index advice. Passschema(CREATE TABLE / CREATE INDEX DDL) for column- and type-aware checks.dialectispostgres(default),mysql,sqlite, ormssql.diff(sql_a, sql_b, schema?, dialect?)— returns a JSON verdict:overallis one ofEquivalent,EquivalentWithNotes,Differs,Undecided, plus a confidence and a per-property report (columns, rows, cardinality, order).
Or via the CLI (@sqlike/cli): sqlike check query.sql --remote https://api.sqlike.com and
sqlike diff before.sql after.sql.
Reading the results
- analyze findings have a severity (high/medium/low) and category (validity, correctness, performance, maintainability, portability). Treat high/validity as must-fix; report the rest with the query. Some findings carry an auto-applicable rewrite — prefer it.
- diff verdicts:
Equivalent= safe to swap.EquivalentWithNotes= same rows/data but a cosmetic difference (column names, ordering) — call it out.Differs= do NOT swap; the results change.Undecidednever means equivalent — sqlike couldn't prove it either way, so treat the rewrite as unverified and say so; don't claim the queries are equivalent.
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.
- 8d ago First seen · 53 lines · 81 tokens per session scan A 33d3f5a7d338
sqlike is a skill published in the GitHub repository orifisher2/sqlike (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 772 once invoked, about $0.0004 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
database
This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
patterns
This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", "add configuration", or builds features involving database operations, REST/GraphQL APIs, pub/sub patterns, or service configuration. Provides implementation patterns that…
migration-audit
Stack-aware migration safety audit: data loss risks, destructive ops without rollback, NOT NULL without DEFAULT, unsafe ALTER TYPE, lock-heavy DDL, constraint sequencing. Supports Prisma, Drizzle, Supabase CLI, raw SQL.
databases
Work with PostgreSQL, MongoDB, and Redis for schema design, query optimization, migrations, and data modeling. Use when designing or optimizing data layers.
israeli-postgres-toolkit
Best practices for PostgreSQL in Israeli apps, covering Supabase patterns, Hebrew text indexing with ICU collation, shekel/NIS currency handling, Israeli date formats, and Asia/Jerusalem timezone gotchas. Use when user asks to "set up Hebrew full-text search", "handle NIS currency in Postgres", "tipul b'ivrit…
ponytail-review
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this…