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.
git clone --depth 1 https://github.com/dagster-io/skillsWrote 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/plugins/dagster-io/skills/marketplace)<a href="https://agentmods.dev/plugins/dagster-io/skills/marketplace"><img src="https://agentmods.dev/badge/plugins/dagster-io/skills/marketplace/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/plugins/dagster-io/skills/marketplace"><img src="https://agentmods.dev/badge/plugins/dagster-io/skills/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dagster marketplace 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 1mo 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
{
"name": "dagster",
"owner": {
"name": "Dagster"
},
"description": "Dagster skills for CLI operations, best practices, and integrations. Dagster+ MCP server included for direct access to your deployment data.",
"plugins": [
{
"name": "dagster",
"source": {
"source": "git-subdir",
"url": "https://github.com/dagster-io/skills.git",
"path": "plugins/dagster",
"ref": "release-stable"
},
"description": "Comprehensive Dagster development conventions and best practices, with the Dagster+ MCP server bundled for querying your deployment."
},
{
"name": "dagster-expert",
"source": "./plugins/dagster-expert",
"description": "Deprecated. Install dagster@dagster instead, then uninstall this plugin."
}
]
}
The plugins it lists here
This marketplace lists 2 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +11 lines 873c057c077c
- 1mo ago First seen · 14 lines scan A 6173a5a12cc7
dagster marketplace is a plugin published in the GitHub repository dagster-io/skills (215 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
evals
LLM evaluation methodology and eval-suite design, based on Anthropic's evaluation guidance. /evals:methodology answers questions on success criteria, eval design, and grading. /evals:design interviews for measurable success criteria and scaffolds a graded eval suite for an LLM app or Claude Code skill.…
context-guard
Per-session context-window observability. A mod writes each session's context-window figures to a snapshot file and shows the person a toast and a transcript line when the context zone (smart, acceptable or dumb, from bands in zones.json) worsens; with modelnotices on (off by default) it also tells Claude the zone at.
desktop-notification
Alert you when Claude Code needs input: an audible terminal bell, an OSC 9 terminal notification, and an OS-native toast (macOS/Linux) on permission and idle prompts.
instruction-placement
Routes agent instructions to the surface that loads them at the right time. audit finds conventions narrower than the always-loaded CLAUDE.md or AGENTS.md, or stranded in docs Claude never loads, and proposes a destination with a validated paths glob; safety content is never demoted. realign applies each move and…
ai-briefing
Build source-backed AI-industry briefings from official vendor publications, configured RSS/Atom feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Deduplicate, rank, and present results as markdown or optional HTML/PPTX decks, with repository-owned profile, audience, and brand…
docs-hygiene
Documentation-hygiene toolkit: compress (trim markdown with a semantic-diff check), audit-noise (classify markdown noise), extract-ssot (deduplicate into a single source of truth), audit-encapsulation (citations into skill-private files), rename-references (stale references after renames), audit-derivability (does a…