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/dagster)<a href="https://agentmods.dev/plugins/dagster-io/skills/dagster"><img src="https://agentmods.dev/badge/plugins/dagster-io/skills/dagster/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/dagster"><img src="https://agentmods.dev/badge/plugins/dagster-io/skills/dagster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dagster 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 today.
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",
"description": "Comprehensive Dagster development conventions and best practices, with the Dagster+ MCP server bundled for querying your deployment.",
"version": "1.13.1",
"author": {
"name": "Dagster",
"url": "https://github.com/dagster-io/skills"
},
"homepage": "https://github.com/dagster-io/skills",
"repository": "https://github.com/dagster-io/skills",
"license": "Apache-2.0",
"keywords": ["dagster", "data-pipelines", "assets", "orchestration", "dg-cli", "mcp"]
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- today First seen · 14 lines scan A c879eceef6bf
dagster is a plugin published in the GitHub repository dagster-io/skills (203 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-09-11.
Other plugins, from other repositories
evals
LLM evaluation methodology and eval-suite design, distilled from Anthropic's official evaluation guidance — a knowledge router over success criteria, eval design, and grading methods (/evals:methodology), plus an action skill that interviews for measurable success criteria and scaffolds a graded eval suite for an LLM…
devops-tools
DevOps automation: ClickHouse, Doppler, MLflow, Cloudflare Workers, pueue orchestration, notifications, session recovery, MiniMax consensus analysis.
instruction-placement
Routes agent-instruction content to the surface that loads it at the right moment. The audit skill sweeps a repository's instruction layer and its ordinary markdown for content whose scope is narrower than the surface carrying it — conventions keyed to one file type or one subtree sitting in an always-loaded CLAUDE.md.
context-guard
Per-session context-window observability plus the first shipped consumer: a statusline wrapper tees each session's contextwindow fields to a per-session snapshot file, a zone resolver classifies usage into smart/acceptable/dumb bands (percentage bands plus window-class token bands, conservative-min combination, zones.
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…
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.