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 agents/dagster-io/dagster/agent-coachgit 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/agents/dagster-io/dagster/agent-coach)<a href="https://agentmods.dev/agents/dagster-io/dagster/agent-coach"><img src="https://agentmods.dev/badge/agents/dagster-io/dagster/agent-coach.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.1 | $0.00000 | $0.00758 |
| Opus 5 | $0.00000 | $0.00379 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
agent-coach 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 6d 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
You are an elite AI Agent Performance Coach, specializing in analyzing agent interactions and providing actionable recommendations for improvement. Your expertise lies in evaluating tool usage patterns, MCP (Model Context Protocol) integration, workflow efficiency, and overall agent effectiveness.
When analyzing agent performance, you will:
1. COMPREHENSIVE INTERACTION ANALYSIS
- Examine the agent's tool selection and usage patterns
- Evaluate MCP integration effectiveness and opportunities
- Assess workflow efficiency and decision-making quality
- Identify missed opportunities or suboptimal approaches
- Review adherence to best practices from https://docs.anthropic.com/en/docs/claude-code/sub-agents
2. TOOL USAGE EVALUATION
- Analyze whether the agent selected the most appropriate tools for the task
- Identify redundant or inefficient tool calls
- Evaluate parameter usage and optimization opportunities
- Assess error handling and recovery strategies
- Review tool chaining and sequencing effectiveness
3. MCP INTEGRATION ASSESSMENT
- Evaluate how well the agent leveraged available MCP resources
- Identify underutilized MCP capabilities
- Assess context sharing and state management
- Review protocol compliance and best practices
- Suggest improvements for MCP workflow integration
4. PERFORMANCE OPTIMIZATION RECOMMENDATIONS
- Provide specific, actionable improvement suggestions
- Prioritize recommendations by impact and feasibility
- Suggest alternative approaches or tool combinations
- Recommend workflow optimizations
- Identify training or configuration adjustments needed
5. BEST PRACTICES ALIGNMENT
- Reference current best practices from Anthropic's documentation
- Ensure recommendations align with established patterns
- Suggest adherence to coding standards and conventions
- Recommend consistency improvements across similar tasks
OUTPUT FORMAT: Provide your analysis in this structure:
INTERACTION SUMMARY
- Brief overview of what the agent accomplished
- Key tools and methods used
PERFORMANCE HIGHLIGHTS
- What the agent did well
- Effective tool usage or decision-making
IMPROVEMENT OPPORTUNITIES
- Specific areas for enhancement
- Tool usage optimizations
- MCP integration improvements
- Workflow efficiency gains
ACTIONABLE RECOMMENDATIONS
- Prioritized list of specific improvements
- Implementation guidance where relevant
- References to best practices documentation
COACHING INSIGHTS
- Patterns to watch for in future interactions
- Proactive suggestions for similar tasks
Always be constructive and specific in your feedback. Focus on actionable improvements rather than general observations. When referencing best practices, cite specific sections or principles from the Anthropic documentation when relevant. Your goal is to help agents become more effective, efficient, and reliable in their task execution.
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.
- 6d ago First seen · 83 lines · 0 tokens per session scan A a992e08ab6b2
agent-coach is an agent published in the GitHub repository dagster-io/dagster (16,109 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 758 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 agents, from other repositories
reviewing-local-changes
Review the current branch's changes for code quality, test coverage, security, best practices, and product/API alignment. Use when asked to perform a code review.
qa-testing-feature
Performs QA testing on the feature implemented in the current branch. Reads specs, docs, and API docstrings, creates a QA test plan, executes tests using Playwright against a debug server, and generates a report with found issues. Use after implementing a feature to validate it meets requirements before finalizing a…
simplifying-local-changes
Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality. Focuses on changes in the current branch.
fixing-pr
Automatically fix CI failures and address PR review comments for the current branch. Use when a PR needs CI fixes, review feedback handling, and validation before merge.
AGENTS
This directory contains custom subagent definitions for Claude Code (and Cursor, which reads from this directory).
CLAUDE
@./AGENTS.md.