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/write_pr_summary.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/write_pr_summary)<a href="https://agentmods.dev/commands/dagster-io/dagster/write_pr_summary"><img src="https://agentmods.dev/badge/commands/dagster-io/dagster/write_pr_summary/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/write_pr_summary"><img src="https://agentmods.dev/badge/commands/dagster-io/dagster/write_pr_summary.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.00000 | $0.00235 |
| Opus 5.5 | $0.00000 | $0.00094 |
| Sonnet 5.5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
write_pr_summary 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 2mo 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
Write PR summary
Use gt ls -s to determine the last git ref in the stack. View all changes since that ref with git diff. Also view the commit messages with git log. Use this context, alongside any session context from what you know about the changes to write a PR summary in Markdown, of the format
## Summary & Motivation
[Brief summary of changes here, including code sample, if a new API was added, etc.]
## How I Tested These Changes
[Very brief summary of test plan here, e.g. "New unit tests.", "New integration tests.", "Existing test suite." This can be a single sentence.]
## Changelog
[End user facing changelog entry, remove this section if no public-facing API was changed and no bug was fixed. Public-facing APIs are identified by the @public decorator. Ignore minor changes. If there are no user-facing changes, remove this section.]
Use bullet points sparingly, and do not overuse italics/bold text. Use short sentences. Output the new markdown to the user so they can copy and paste it into the PR.
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.
- 2mo ago First seen · 20 lines · 0 tokens per session scan A a6cf1ae45cd1
write_pr_summary is a command published in the GitHub repository dagster-io/dagster (16,348 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 235 tokens. 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
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
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.
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.
release-tag
Create and push a version tag after a release PR has been merged.
autotask
Execute development task autonomously from description to PR-ready - handles implementation, testing, and git workflow without supervision.
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.