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.
/plugin marketplace add covagashi/eplan-rag-mcpnpx agentmods add plugins/covagashi/eplan-rag-mcp/eplan-developmentgit clone --depth 1 https://github.com/covagashi/eplan-rag-mcpGrade A, and why
eplan-development 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 3d 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": "eplan-development",
"description": "Develop with EPLAN Electric P8: C# scripting (actions, events, ribbon), EPLAN API (parts database, properties), and Remote Client automation (headless EPLAN, Cogineer). Includes verified action parameters and production pitfalls (command blocking, dispose discipline, EPLAN 2025 remoting changes). Covers EPLAN 2022-2025.",
"version": "1.0.0",
"author": {
"name": "covagashi",
"url": "https://github.com/covagashi"
},
"homepage": "https://github.com/covagashi/Eplan_2026_IA_MCP_scripts/tree/main/claude-skills/eplan-development",
"repository": "https://github.com/covagashi/Eplan_2026_IA_MCP_scripts",
"license": "MIT",
"keywords": [
"eplan",
"eplan-p8",
"eplan-electric",
"electrical-engineering",
"csharp",
"scripting",
"automation",
"cogineer",
"remoting"
]
}
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.
- 3d ago First seen · 24 lines scan A 65df6167401b
eplan-development is a plugin published in the GitHub repository covagashi/eplan-rag-mcp (77 stars, last pushed 12d ago), 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-08-30.
Other plugins, from other repositories
CrestApps.AgentSkills marketplace
Shared AI agent skills and MCP tooling for .NET applications and Orchard Core based projects. The repository contains three projects that solve distinct problems.
dotnet-aspnetcore
ASP.NET Core web development skills including middleware, endpoints, real-time communication, and API patterns.
aiup-blazor-dotnet
AI Unified Process for the C# / Blazor .NET 10 stack - migrations, implementation, tests.
rocm
AMD ROCm 7.2.4 GPU computing stack: HIP kernel development, rocBLAS/rocFFT/rocRAND/rocSOLVER compute libraries, profiling, and CUDA-to-HIP porting.
dotnet-episteme-skills
Practical, production-tested .NET skills that provide enterprise-proven instructions for AI-assisted development.
code-review
Autonomous C#/.NET code review — fail-fast pipeline with mechanical checks + AI sub-agents (performance, architecture, correctness, UI/Blazor).