What is build-scaling-experiment?

A skill for building and submitting benchmark experiments that measure how a system changes as the data size grows. It provides templates and scripts for database scaling tests.

Testing whether performance grows linearly, comparing sizes from N to M rows, and finding the data size at which a system becomes too slow or fails.

It gives scaling investigations a defined process instead of requiring experiment files and database test plans to be created from scratch.

build-scaling-experiment — Skill for Claude Code and Codex by rctruta

Install

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.

Any agent

npx skills add rctruta/sql-benchmarks-dagster --skill build-scaling-experiment

Clone the repo

git clone --depth 1 https://github.com/rctruta/sql-benchmarks-dagster

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rctruta/sql-benchmarks-dagster/build-scaling-experiment/github.svg)](https://agentmods.dev/skills/rctruta/sql-benchmarks-dagster/build-scaling-experiment)

Your own site

<a href="https://agentmods.dev/skills/rctruta/sql-benchmarks-dagster/build-scaling-experiment"><img src="https://agentmods.dev/badge/skills/rctruta/sql-benchmarks-dagster/build-scaling-experiment/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rctruta/sql-benchmarks-dagster/build-scaling-experiment"><img src="https://agentmods.dev/badge/skills/rctruta/sql-benchmarks-dagster/build-scaling-experiment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 785 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.00785
Opus 5.5	$0.00021	$0.00314
Sonnet 5.5	$0.00010	$0.00157
Haiku 4.5	$0.00005	$0.00078

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

Security

Grade A, and why

build-scaling-experiment 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.

skills/build-scaling-experiment/SKILL.md · 52 lines

How it starts

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

Skill: build a scaling experiment

Use when: the goal names a scale-varying investigation ("how does X scale from N to M rows", "is the growth linear", "at what size does Y break").

Do NOT construct YAML from scratch. Fetch a template, adapt it. quickstart (DuckDB-only) and scaling_depth (multi-engine) are the two scaling starters — list_templates names them all.

Recipe

python scripts/list_categories.py → the vocabulary is small. For scaling questions, scaling is the tag. For cross-engine investigations, also cross-engine. For selectivity/index behavior, selectivity.
python scripts/list_suites.py --category <name> → returns only the suites tagged with that category, without SQL bloat. For "analytical aggregation scaling", python scripts/list_suites.py --category scaling narrows to analytical_wall and any other scaling-tagged suite. NEVER call list_suites.py without a category unless you have no idea what you're looking for — an unfiltered call is expensive.
python scripts/list_templates.py → python scripts/get_template.py quickstart (DuckDB-only, no Docker) OR python scripts/get_template.py scaling_depth (multi-engine, needs Docker). Use quickstart unless the question requires Postgres.
Adapt the fetched YAML: keep dataset.tables.*.rows as the string alias rows (not a literal integer); add the scale points you want to definitions.rows; list them in execution.matrix.rows.
python scripts/submit_experiment.py --yaml-file <path> with the adapted YAML.
python scripts/get_experiment_status.py <exp_id> until complete or failed.

Adapt-template pattern

Start from quickstart and change three things:

definitions:
  rows:
    small:  100_000     # add/rename scale points here
    medium: 1_000_000
    large:  10_000_000

execution:
  test_suite: analytical_wall     # match the question's shape
  engines:
    - duckdb                       # add postgres/quack only if the question needs cross-engine
  replication: 5                   # 5 is a good default; 3 for quick sanity, 10 for a paper
  matrix:
    rows:
      - small                      # every value here MUST exist as a key under definitions.rows
      - medium
      - large

Read the full file on GitHub · 52 lines

Files

What ships with it

1 file 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.

scaling_duckdb.yaml 1005 B

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.

1mo ago First seen · 52 lines · 52 tokens per session scan A 2b0aba31a2bb

Subscribe to this mod's changes

build-scaling-experiment is a skill published in the GitHub repository rctruta/sql-benchmarks-dagster (2 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 785 once invoked, about $0.0002 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-31.

Analytics and metrics Scientific benchmarks dagster docker-compose duckdb postgresql sql

duckdb

Run embedded OLAP SQL on Parquet/CSV locally; configure memory and thread limits; attach remote files safely; export with COPY; avoid multi-writer locks and treating DuckDB as a production server database.

alivirgo/Major-AI-Skills · 45 tokens

graphjin-eval

Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.

dosco/graphjin · 27 tokens

graphjin-env

Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.

dosco/graphjin · 61 tokens

network-data-analysis

Ad-hoc read-only SQL analysis over exported network data (Zeek logs, Suricata eve.json, generated reports) using DuckDB. Use when aggregating across a packet capture's sessions, correlating IDS alerts with connection metadata, or answering counting and grouping questions that a per-log view cannot.

automateyournetwork/netclaw · 64 tokens

sun-simiao-perspective

A historical medical-perspective skill based on research about Sun Simiao, a physician from China's Tang dynasty. It uses his clinical ideas and writings to discuss traditional Chinese medicine, health advice, medical ethics, and communication with patients.

digoal/blog · 950 tokens

enrich-context

Augment a Wren project with business context that DB schema cannot carry — enum value meanings, units (USD vs cents, ms vs sec), NULL semantics, magic sentinels (-1 = unknown), soft-delete default filters, business synonyms, time-grain / TZ conventions, cross-system identifiers, currency rules, canonical-table…

Canner/WrenAI · 347 tokens