Borrowing it
Nothing to install: this file belongs to Kemetra/Seshat-BI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kemetra/Seshat-BI/main/.claude/skills/dagster-orchestration-adapter/SKILL.mdgit clone --depth 1 https://github.com/Kemetra/Seshat-BIWrote 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/kemetra/seshat-bi/dagster-orchestration-adapter)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/dagster-orchestration-adapter"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/dagster-orchestration-adapter/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/kemetra/seshat-bi/dagster-orchestration-adapter"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/dagster-orchestration-adapter.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.00186 | $0.05579 |
| Opus 5 | $0.00093 | $0.02789 |
| Sonnet 5 | $0.00037 | $0.01116 |
| Haiku 4.5 | $0.00019 | $0.00558 |
Grade A, and why
dagster-orchestration-adapter 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 11d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dagster-orchestration-adapter
- Authority category (F024): Execution Adapter /
DB-connected(NOT publish-capable; it TRIGGERS F016, it never publishes). The F024 enumerated declaration -- seedocs/architecture/product-modules.md. - Roadmap feature: F030 On-disk spec:
specs/024-dagster-orchestration-adapter(dir 024 == F030; when the dir number and the F-number disagree, the roadmap F-number wins).
Dagster is the unattended / CI RUNTIME for the medallion sequence: a scheduler / pipeline runs
the asset graph so a human does not re-type each step. retail-orchestrate (F005) is the
INTERACTIVE conductor of the SAME sequence; Dagster is its unattended sibling -- same medallion
sequence, same gate-exit authority, same two human seams, neither self-approving. Tower BI (the
gate exit code + the named human) is the brain; Dagster is the runner. This skill is how the
agent reasons about running the medallion unattended without letting the orchestrator become the
brain. You (the agent reading this) ARE the design surface; this skill is procedure, not an
engine -- the engine, when built, is the separate Dagster project. See
docs/decisions/0010-dagster-is-orchestration-adapter.md and
docs/integrations/dagster-adapter.md.
STATUS: the Dagster PROJECT is BUILT (spec 134, activation slice of F030; the dbt engine seam is ACTIVATED per spec 135).
orchestration/dagster/exists --definitions.py, the 11-asset graph,jobs, one STOPPED schedule, one STOPPED sensor,pyproject.tomlpinningdagster==1.13.14and bringingseshat-bi[dbt](thedagster-dbtpin was dropped by spec 135 FR-011: it excludes dbt-core 1.12 and sits on no execution path) -- plus theseshat dagster doctor|run|evidencecontrol layer. The OPERATIONAL procedure:
seshat dagster doctor-- read-only preflight (project, its own venv underorchestration/dagster/.venv, the pinned dagster, the resolved build engine per table, per-table gate state, DSN present/absent). Blockers exit 2; the install remedy iscd orchestration/dagster && uv venv .venv && uv pip install -p .venv -e "../..[dbt]" -e ".[dev]".seshat dagster run --job <full_sequence_job|through_gold_job> [--table <table>]-- executes the graph as a shell-free child process in the orchestration venv. A failed/blocked gate halts downstream assets and exits 3 (the CI signal); report it with the recorded blocking_reason + named owner.seshat dagster evidence [--run-id <id>]-- list runs / render the committed record atorchestration/dagster/run-evidence/<run-id>.md.Without DB credentials the DB-touching assets record a deferred boundary and block fail-closed -- report that truthfully; never fake a run.
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.
- 11d ago First seen · 349 lines · 186 tokens per session scan A 4bd73a2dea99
dagster-orchestration-adapter is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 186 tokens to every session and 5,579 once invoked, about $0.0009 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
ktx-analytics
Use when answering a question that needs data from a ktx-connected database - investigating, analyzing, "how many", "show me", "what's the breakdown of", finding records by value, exploring tables, comparing periods, explaining metrics, or any data-analysis request. Triggers even when the user does not say…
metabase_ingest
Convert Metabase questions, models, and metrics into ktx Semantic Layer source definitions. Covers result-metadata to KSL column type mapping, FK/PK detection, near-duplicate deduplication, pre-aggregation decomposition, join-graph connectivity, and how to react to priorProvenance from earlier ingest syncs. Load when…
sl_capture
How to capture new reusable patterns into ktx's semantic layer - when a measure, segment, or join belongs in the catalog and how to write it generically so it stays small and useful over time. Loaded by the post-turn memory-agent only. The research agent does not write to the SL.
looker_ingest
Extract durable ktx knowledge and semantic-layer contribution proposals from staged Looker runtime dashboard, Look, and explore JSON. Load for WorkUnits whose raw files are under explores/, dashboards/, or looks/.
metricflow_ingest
Map a MetricFlow semanticmodel or metric into ktx semantic layer sources. Covers the MetricFlow to ktx primitive table, extends: inheritance flattening, metric-type handling (simple / derived / ratio / cumulative / conversion), model: ref('x') resolution, and four worked examples. Load when the turn contains…
lookml_ingest
Map a LookML view/model/explore into ktx semantic layer sources. Covers the LookML to ktx primitive table, provenance tagging, and three worked examples (overlay, standalone from derivedtable, standalone with sqlalwayswhere). Load when the turn contains .lkml content.