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/justanesta/claude-code-resources/sql-data-modelingnpx skills add justanesta/claude-code-resources --skill sql-data-modelinggit clone --depth 1 https://github.com/justanesta/claude-code-resourcesWhat 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.00083 | $0.02388 |
| Opus 5 | $0.00042 | $0.01194 |
| Sonnet 5 | $0.00017 | $0.00478 |
| Haiku 4.5 | $0.00008 | $0.00239 |
Grade A, and why
sql-data-modeling 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Data Modeling
Essential patterns for designing robust, performant database schemas.
Core Principles
- Model the business domain first - Tables should reflect real-world entities and relationships
- Normalize for integrity, denormalize for performance - Start normalized, denormalize with evidence
- Enforce constraints at the database level - Never rely solely on application logic for data integrity
- Design for query patterns - Schema should serve the most common read and write workloads
- Plan for change - Use surrogate keys and flexible structures that accommodate evolving requirements
Normalization Fundamentals
-- Unnormalized: repeating groups and mixed concerns
-- orders(order_id, customer_name, customer_email, item1, price1, item2, price2)
-- 1NF: Atomic values, no repeating groups
CREATE TABLE orders (
order_id INT PRIMARY KEY,
customer_id INT NOT NULL,
order_date DATE NOT NULL
);
CREATE TABLE order_items (
order_item_id INT PRIMARY KEY,
order_id INT NOT NULL REFERENCES orders(order_id),
product_name VARCHAR(200) NOT NULL,
unit_price NUMERIC(10,2) NOT NULL,
quantity INT NOT NULL CHECK (quantity > 0)
);
-- 2NF: Remove partial dependencies (every non-key depends on full PK)
-- 3NF: Remove transitive dependencies (non-key columns depend only on the PK)
CREATE TABLE customers (
customer_id INT PRIMARY KEY,
name VARCHAR(100) NOT NULL,
email VARCHAR(255) NOT NULL UNIQUE
);
CREATE TABLE products (
product_id INT PRIMARY KEY,
product_name VARCHAR(200) NOT NULL,
unit_price NUMERIC(10,2) NOT NULL
);
See normalization-patterns.md for:
- Step-by-step 1NF through BCNF walkthrough
- When to stop normalizing
- Normal form trade-offs and decision criteria
Denormalization Strategies
-- Precomputed summary table for dashboard queries
CREATE TABLE daily_sales_summary (
summary_date DATE NOT NULL,
product_id INT NOT NULL REFERENCES products(product_id),
category_id INT NOT NULL REFERENCES categories(category_id),
total_quantity INT NOT NULL DEFAULT 0,
total_revenue NUMERIC(12,2) NOT NULL DEFAULT 0,
order_count INT NOT NULL DEFAULT 0,
PRIMARY KEY (summary_date, product_id)
);
-- Refresh pattern: truncate and reload daily
INSERT INTO daily_sales_summary (summary_date, product_id, category_id, total_quantity, total_revenue, order_count)
SELECT
o.order_date,
oi.product_id,
p.category_id,
SUM(oi.quantity),
SUM(oi.quantity * oi.unit_price),
COUNT(DISTINCT o.order_id)
FROM orders o
INNER JOIN order_items oi ON o.order_id = oi.order_id
INNER JOIN products p ON oi.product_id = p.product_id
WHERE o.order_date = CURRENT_DATE - INTERVAL '1 day'
GROUP BY o.order_date, oi.product_id, p.category_id;
What ships with it
7 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 · 257 lines · 83 tokens per session scan A 345e2725d5c3
sql-data-modeling is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 4mo ago), licensed MIT. It adds 83 tokens to every session and 2,388 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…