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/squadcodercom/squadcoder/israeli-postgres-toolkitnpx skills add squadcodercom/squadcoder --skill israeli-postgres-toolkitgit clone --depth 1 https://github.com/squadcodercom/squadcoderWhat 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.00199 | $0.05736 |
| Opus 5 | $0.00100 | $0.02868 |
| Sonnet 5 | $0.00040 | $0.01147 |
| Haiku 4.5 | $0.00020 | $0.00574 |
Grade A, and why
israeli-postgres-toolkit 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Israeli Postgres Toolkit
Best practices, patterns, and scripts for building PostgreSQL databases tailored to Israeli applications. Covers Hebrew text handling, NIS currency, Israeli timezones, Supabase integration, and common Israeli data types.
Instructions
Follow this workflow when setting up or reviewing a PostgreSQL database for an Israeli app:
- Verify encoding and timezone first. Run
SHOW server_encoding;(must beUTF8, neverSQL_ASCIIorLATIN1) andSHOW timezone;. Set the database timezone withALTER DATABASE your_db SET timezone = 'Asia/Jerusalem';. Getting these wrong corrupts Hebrew and offsets every timestamp, and fixing it later means a data migration. - Pick the collation strategy. Decide per column whether you need Hebrew display ordering (non-deterministic ICU collation
he-IL-x-icu) or uniqueness/btreeindexing (deterministic collation). You usually need both, on different columns or via separate indexes, because a non-deterministic collation cannot back aUNIQUEconstraint or a plainbtreeindex. - Choose the search approach. For exact and prefix matching use
btree. For fuzzy/typo-tolerant Hebrew search usepg_trgm. For multi-field ranked search use full-text search with thesimpleconfiguration (see "Full-Text Search with Hebrew" below). Combineunaccentwhen you need nikud-insensitive matching. - Apply Israeli data-type constraints. Use the
CHECKconstraints and helper functions fromscripts/israeli-data-types.sql(teudat zehut, phone, postal code, business number, IBAN) and callvalidate_teudat_zehut()for the ID check digit rather than reimplementing it in application code.
Hebrew Text Indexing
ICU Collation for Hebrew
PostgreSQL supports ICU collations for proper Hebrew text sorting. Always create a Hebrew collation for columns that store Hebrew text:
-- Create Hebrew ICU collation
CREATE COLLATION IF NOT EXISTS hebrew_icu (
provider = icu,
locale = 'he-IL-x-icu',
deterministic = false
);
-- Use on columns
CREATE TABLE products (
id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
name_he text COLLATE hebrew_icu NOT NULL,
name_en text NOT NULL
);
-- Or apply in queries
SELECT * FROM products ORDER BY name_he COLLATE hebrew_icu;
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 550 lines · 199 tokens per session scan A faaa8e192314
israeli-postgres-toolkit is a skill published in the GitHub repository squadcodercom/squadcoder (11 stars, last pushed 2mo ago), licensed MIT. It adds 199 tokens to every session and 5,736 once invoked, about $0.0010 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
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…