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/draugr-dev/draugrWrote 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/draugr-dev/draugr/claude-plugin)<a href="https://agentmods.dev/plugins/draugr-dev/draugr/claude-plugin"><img src="https://agentmods.dev/badge/plugins/draugr-dev/draugr/claude-plugin/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/draugr-dev/draugr/claude-plugin"><img src="https://agentmods.dev/badge/plugins/draugr-dev/draugr/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
draugr 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 2d 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": "draugr",
"displayName": "Draugr",
"version": "0.151.0",
"description": "Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.",
"author": {
"name": "Draugr",
"url": "https://draugr.dev"
},
"homepage": "https://draugr.dev",
"documentationUrl": "https://draugr.dev/docs/latest/guides/ai-agents-mcp/",
"supportUrl": "https://github.com/draugr-dev/draugr/issues",
"privacyPolicyUrl": "https://draugr.dev/privacy/",
"termsOfServiceUrl": "https://draugr.dev/terms/",
"repository": "https://github.com/draugr-dev/draugr",
"license": "Apache-2.0",
"keywords": [
"security",
"sast",
"sca",
"sarif",
"devsecops",
"vulnerability"
],
"mcpServers": {
"draugr": {
"command": "draugr",
"args": [
"mcp"
]
}
}
}
What it installs
The manifest is a name and a version. 1 hook 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 ships with it
1 file beside plugin.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.
- 2d ago Changed 3371f6a99faa
- 5d ago Changed 8869b544906d
- 7d ago Changed b5a30c0744a2
- 8d ago Changed 0ff2a74c7c05
- 10d ago Changed ad9b75937ad6
- 12d ago Changed 21ac0181e253
- 13d ago Changed ae0637e711b5
- 14d ago Changed cb68d553a59c
- 16d ago Changed 670e6041c5b2
- 17d ago First seen · 34 lines scan A 16a9e6b53473
draugr is a plugin published in the GitHub repository draugr-dev/draugr (7 stars, last pushed yesterday), 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-26.
Other plugins, from other repositories
shor
Shor — autonomous AI web pentester. Provides the /shor-setup slash-command: an interactive wizard that guides you from zero to a running scan (black-box or white-box, GCP deployment included).
fortify-skills
OpenText Fortify AppSec skills. Use for SAST/DAST/SCA scanning, vulnerability triage, audit workflows, CI/CD pipeline integration, and FCLI commands. Supports Fortify on Demand (FoD) and Software Security Center (SSC).
fettle
In-session quality governance for AI-assisted development, with advisory-first code and process gates, evidence, and multi-agent controls.
cloud-security-gcp
Defensive Google Cloud security: IAM and Workload Identity, Organization Policies, VPC Service Controls, and CIS GCP benchmark audits.
devsecops-pipelines
Security-integrated CI/CD: pipeline security architecture, SAST, SCA, secrets, IaC, and container scanning in GitHub Actions, GitLab CI, and Jenkins, and build-breaking security gates.
forensics-analysis
Digital forensics for authorized investigations: investigation planning, chain of custody, disk and artifact analysis, timelines, and memory forensics with Volatility.