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/pr-submitgit 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/pr-submit)<a href="https://agentmods.dev/commands/dagster-io/dagster/pr-submit"><img src="https://agentmods.dev/badge/commands/dagster-io/dagster/pr-submit.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.00020 | $0.00298 |
| Opus 5 | $0.00010 | $0.00149 |
| Sonnet 5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
pr-submit 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.
What it actually says
Submit PR
Automatically create a git commit with a helpful summary message and submit the current branch as a pull request.
Note: This command squashes commits and rebases the stack. If you prefer a simpler workflow that preserves your commit history, use /erk:git-pr-push instead.
Usage
# Invoke the command (description argument is optional but recommended)
/erk:pr-submit "Add user authentication feature"
# Without argument (will analyze changes automatically)
/erk:pr-submit
Implementation
This command delegates to erk pr submit which handles everything:
- Preflight checks (auth, squash commits, submit to Graphite)
- AI-powered commit message generation
- PR metadata update with title and body
- PR validation
Execute
Run the full submit workflow:
erk pr submit
Report Results
The command outputs:
- PR URL
- Graphite URL
- Success message
Error Handling
If erk pr submit fails, display the error and stop. The Python implementation handles all error cases including:
- Authentication issues (Graphite/GitHub)
- Merge conflicts
- No commits to submit
- Submission failures
Do NOT attempt to auto-resolve errors. Let the user fix issues and re-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.
- 4d ago First seen · 59 lines · 20 tokens per session scan A 4bcb22da46b0
pr-submit is a command published in the GitHub repository dagster-io/dagster (16,073 stars, last pushed 7d ago), licensed Apache-2.0. It adds 20 tokens to every session and 298 once invoked, about $0.0001 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 commands, from other repositories
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
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.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…