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/nevaberry/nevaberry-plugins/dagster-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill dagster-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/dagster-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/dagster-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/dagster-knowledge-patch.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.01908 |
| Opus 5 | $0.00005 | $0.00954 |
| Sonnet 5 | $0.00002 | $0.00382 |
| Haiku 4.5 | $0.00001 | $0.00191 |
Grade A, and why
dagster-knowledge-patch 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 4d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dagster Knowledge Patch
Use this skill when upgrading or maintaining Dagster definitions, Components, automation, execution infrastructure, storage, deployment configuration, or integration packages. Check the installed Dagster and integration-package versions first, then open the reference that matches the task.
Working Method
- Inspect
dagster, integration-package, Python, and deployment-chart versions. - Identify removed or renamed APIs before changing behavior.
- Validate definitions with
dg checkor the applicable definitions command. - For daemon, executor, storage, or launcher changes, test failure and retry paths.
- Consult the topic references for exact settings, defaults, and integration details.
Reference Index
| Reference | Topics |
|---|---|
| Assets and automation | Asset definitions, checks, freshness, partitions, selections, ownership, and automation |
| Components and CLI | Components, templates, scaffolding, dg, configuration, and API queries |
| Deployment and storage | Helm, Kubernetes, ECS, databases, authentication, state, and storage defaults |
| Execution and operations | Coordinators, pools, executors, backfills, GraphQL, logs, sensors, and Pipes |
| Integrations | dbt, Airbyte, Fivetran, Databricks, BI tools, IO managers, and other packages |
| Upgrade and compatibility | Removed APIs, renamed settings, package lifecycle, Python, and dependency requirements |
Upgrade-Critical Changes
Run launching requires the daemon by default
The queued run coordinator is the default. Ensure the Dagster daemon is running, or explicitly restore immediate in-process launching:
run_coordinator:
module: dagster.core.run_coordinator.sync_in_memory_run_coordinator
class: SyncInMemoryRunCoordinator
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.
- 4d ago First seen · 229 lines · 9 tokens per session scan A da7f38d0f7ae
dagster-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 1,908 once invoked, about $0.0000 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
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.