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/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/dometrain)<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/dometrain"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/dometrain/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/melodic-software/claude-code-plugins/dometrain"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/dometrain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dometrain 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "dometrain",
"version": "0.2.11",
"description": "Dometrain course-content grounding over a third-party remote MCP server (Dometrain-hosted, Bearer auth): search lessons, pull curated lesson documents with on-screen code, and cite timestamped deep links. Requires an active Dometrain Pro subscription. Credential entered once through Claude Code's native masked userConfig prompt and stored in secure credential storage. Ships with a grounding usage skill kept in sync with Dometrain's own official Claude Code plugin.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"dometrain",
"mcp",
"courses",
"dotnet",
"csharp",
"learning"
],
"defaultEnabled": false,
"userConfig": {
"dometrain_api_key": {
"type": "string",
"title": "Dometrain API key",
"description": "Dometrain account API key from https://dometrain.com/dashboard/account/ (MCP API keys section). Required \u2014 the remote MCP server rejects requests without it. Stored by Claude Code in secure credential storage, never settings.json.",
"sensitive": true,
"required": true
}
}
}
What it installs
The manifest is a name and a version. 2 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 159 tokens a session between 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 Changed 6e13ec8caa48
- 2d ago Changed 5c8e7c6c6965
- 5d ago First seen · 30 lines scan A 424e1a72d5de
dometrain is a plugin published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. 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-03.
Other plugins, from other repositories
collaborative-planning
Collaborative planning commands with iterative requirements gathering. Ensures thorough understanding before implementation through structured Q&A sessions.
local-llm
Manage local Ollama LLM models for development and testing.
parallel-workflows
Parallel workflow orchestration using git worktrees for concurrent Claude Code sessions.
deep-research
Iterative deep research with progressive exploration and structured synthesis.
error-therapist
Audit and rewrite error messages to be helpful and actionable.
content
Content creation and publishing: three writer+optimiser pairs (guides, features, documentation) with research-first workflows, per-content reports, and deterministic audit scoring. Feature writer+optimiser now enforce Technical-Marketing Synthesis (Rule 6: ten sub-checks including coined terminology, dropdown…