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.
Borrowing it
Nothing to install: this file belongs to dagster-io/dagster. 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/dagster-io/dagster/master/.claude/commands/erk/objective-update-with-landed-pr.mdgit 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/objective-update-with-landed-pr)<a href="https://agentmods.dev/commands/dagster-io/dagster/objective-update-with-landed-pr"><img src="https://agentmods.dev/badge/commands/dagster-io/dagster/objective-update-with-landed-pr/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/commands/dagster-io/dagster/objective-update-with-landed-pr"><img src="https://agentmods.dev/badge/commands/dagster-io/dagster/objective-update-with-landed-pr.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.00007 | $0.01545 |
| Opus 5 | $0.00003 | $0.00772 |
| Sonnet 5 | $0.00001 | $0.00309 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
objective-update-with-landed-pr 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 10d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/erk:objective-update-with-landed-pr
Update an objective issue after landing a PR from a plan branch.
Usage
Run after landing a PR:
/erk:objective-update-with-landed-pr
Agent Instructions
Step 0: Parse Arguments (if provided)
Check $ARGUMENTS for pre-provided context:
--pr <number>: PR number that was just landed--objective <number>: Objective issue number to update--branch <name>: Original branch name (contains plan issue number inP<number>-...pattern)--auto-close: If set and all steps are complete, close objective without asking
If all arguments are provided: Use them directly. Parse the plan issue number from the branch name pattern to get implementation details. Skip Steps 1 and 4 (discovery steps).
If arguments are not provided: Continue with Steps 1 and 4 to discover from git state (manual invocation case).
Step 1: Get Current Branch and Find Parent Objective
Skip this step if --objective was provided in arguments.
git branch --show-current
Parse the plan issue number from the branch name pattern P<number>-...
Example: P3679-phase-1b-implement-fakes -> Plan Issue #3679
Important: The branch pattern P<number>-... points to an erk-plan issue, not the objective. After getting the plan issue number:
- Read the plan issue:
erk exec get-issue-body <plan-number>(returns JSON with body) - Find the parent objective reference (look for "Objective: #XXXX" or "[#XXXX]" link in the body)
- Use the objective issue number for all subsequent steps
If the branch doesn't match the pattern:
- Ask the user for the objective issue number
- Use AskUserQuestion tool with options like "#3679", "#3680", or "Other"
If the plan issue has no objective reference, ask the user which objective to update.
Step 2: Load Objective Skill
Load the objective skill for format templates and guidelines.
Step 3: Read Current Objective State
erk exec get-issue-body <issue-number>
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.
- 10d ago First seen · 217 lines · 7 tokens per session scan A 031d1a8fd555
objective-update-with-landed-pr is a command published in the GitHub repository dagster-io/dagster (16,132 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 1,545 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 commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
clean-branches
A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.
rollback
An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.
resolve-pr
Resolve PR review feedback — fetch unresolved threads, triage, dispatch resolver agents, reply + resolve via GraphQL.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
analyze-git
Perform a comprehensive analysis of the git repository to identify branches and worktrees that can be cleaned up. This is a READ-ONLY analysis - no deletions will be performed.