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/validate_changed_docstringsgit clone --depth 1 https://github.com/dagster-io/dagsterWhat 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.00000 | $0.00324 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
validate_changed_docstrings 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 2d 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
Validate Changed Docstrings
Validates Python docstrings in all uncommitted changed files using Sphinx parsing.
This command finds files with uncommitted changes (staged or unstaged), extracts Python symbols with docstrings, and validates them using the existing docstring validation tool to catch RST syntax errors and other docstring issues early in development.
Usage
Run the validation script on changed files:
dagster-docs check docstrings --changed
What it does
- Uses
git diff --name-only HEADto find uncommitted Python files - Parses each file's AST to extract classes, functions, and methods with docstrings
- Validates each symbol's docstring using the Sphinx parsing pipeline
- Reports errors and warnings with clear symbol paths
- Returns non-zero exit code if any errors are found
Example output
Found 2 uncommitted Python files:
python_modules/dagster/dagster/_core/definitions/decorators/asset_decorator.py
python_modules/dagster/dagster/_core/definitions/asset.py
Validating 8 symbols with docstrings...
--- dagster._core.definitions.decorators.asset_decorator.asset ---
ERROR: RST syntax: <string>:111: (WARNING/2) Cannot analyze code. No Pygments lexer found for "pythonkjdfkd".
Summary: 1 errors, 0 warnings
✗ Some docstring validations failed
This helps catch docstring issues before they reach the documentation build process.
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.
- 2d ago First seen · 40 lines · 0 tokens per session scan A a74b4479fb12
validate_changed_docstrings is a command published in the GitHub repository dagster-io/dagster (16,073 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 324 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
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.
add-task-module
Scaffold a new task module (classification/regression/clustering/...).
work-on-approved-issue
Pick an Approved GitHub issue and resolve it end-to-end.
run-engine-tests
Fast local test loop for the engine package.
cron
Schedule skills to run automatically at specific times or based on events.