Dagster is a platform for developing, running, and observing data assets, such as datasets and the processes that produce them. It is used to organize and automate data workflows.
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 commands/dagster-io/dagster/fix-conflictsgit clone --depth 1 https://github.com/dagster-io/dagsterWrote 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/commands/dagster-io/dagster/fix-conflicts)<a href="https://agentmods.dev/commands/dagster-io/dagster/fix-conflicts"><img src="https://agentmods.dev/badge/commands/dagster-io/dagster/fix-conflicts.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.00010 | $0.00238 |
| Opus 5 | $0.00005 | $0.00119 |
| Sonnet 5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade C, and why
fix-conflicts scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- prettier-ignore --> What it actually says
Fix Merge Conflicts
Fix all merge conflicts and continue the git rebase.
Steps
-
Check status - Run
git statusto understand the state of the rebase and identify conflicted files -
For each conflicted file:
@../../../.erk/docs/kits/erk/includes/conflict-resolution.md
-
After resolving all conflicts:
- If project memory includes a precommit check, run it and ensure no failures
- Stage the resolved files with
git add - Continue the rebase with
git rebase --continue
-
Loop - If the rebase continues with more conflicts, repeat the process
-
Verify completion - Check git status and recent commit history to confirm success
-
Push changes - After rebase, the branch will have diverged from origin. Push the rebased branch:
- For Graphite users:
gt submit(orgt ss) - For git-only users:
git push --force-with-lease
- For Graphite users:
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.
- 5d ago First seen · 30 lines · 10 tokens per session scan C ef528fc55f9f
fix-conflicts is a command published in the GitHub repository dagster-io/dagster (16,073 stars, last pushed 7d ago), licensed Apache-2.0. It adds 10 tokens to every session and 238 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.