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.
npx agentmods add instructions/draugr-dev/draugr/claude-mdgit 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/instructions/draugr-dev/draugr/claude-md)<a href="https://agentmods.dev/instructions/draugr-dev/draugr/claude-md"><img src="https://agentmods.dev/badge/instructions/draugr-dev/draugr/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.02807 | $0.02807 |
| Opus 5 | $0.01404 | $0.01404 |
| Sonnet 5 | $0.00561 | $0.00561 |
| Haiku 4.5 | $0.00281 | $0.00281 |
Grade A, and why
draugr CLAUDE.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on Draugr
Orientation for AI coding assistants, and a reasonable first read for humans too. CONTRIBUTING.md has the mechanics; this file is the why behind them, which is what keeps them from being applied mechanically.
What Draugr is
A security and compliance qualification tool. You describe your application in a declarative descriptor — the Saga — and Draugr infers which checks apply, runs them, normalizes every result to one schema, and returns a deterministic gated verdict with evidence.
The shape of a run, which is also the shape of the code:
Saga → controllers → scanners → SARIF → Norn → verdict + evidence
(what applies) (run a tool) (one schema) (policy)
- Controllers decide what to check for a component and aggregate the results.
- Scanners run an external tool (Trivy, Semgrep, Gitleaks, Nuclei, Syft…) and normalize its output.
- SARIF 2.1.0 is the finding currency. Everything converges on it before anything is judged.
- The Norn applies policy — thresholds, priorities, suppressions — and produces the verdict.
Layout
pkg/ is the public API; treat changes there as breaking until proven otherwise. internal/ is
implementation and can move freely.
| Package | What lives there |
|---|---|
pkg/saga |
The descriptor: repositories, images, hosts, config, exclusions |
pkg/plugin |
The extension SDK — Scanner, Controller, Surveyor, and shared types |
pkg/sarif |
The finding model, plus merge and deduplication |
pkg/engine |
Expands a Saga into scan jobs and orchestrates the run |
pkg/norn |
Evaluates results against policy to produce a verdict |
pkg/report |
Renders a result: console, markdown, HTML, JUnit, JSON, SARIF |
internal/controllers, internal/scanners |
The built-in controls and the tools behind them |
internal/builtins |
Where both get registered |
A new control is a controller plus a scanner, registered in internal/builtins. Copy the shape
of an existing pair — sca + trivy-fs for a repository tool, images + trivy for one that
scans a named artifact.
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.
- 4d ago First seen · 214 lines · 2,807 tokens per session scan A 289aabe97ac7
draugr CLAUDE.md is an instructions file published in the GitHub repository draugr-dev/draugr (4 stars, last pushed today), licensed Apache-2.0. It adds 2,807 tokens to every session, about $0.0140 per session on Opus 5. 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-31.
Other instructions, from other repositories
Cybermes AGENTS.md
Instructions for Zyrexnn/Cybermes, covering 🛡️ cybermes master operational directives (agents.md), 1. 🎯 persona & core mission, 2. ⚡ core operational principles, 3. 📁 strict target-scoped workspace & deliverables and mandatory rules for file creation.
secure-sdlc-agents CLAUDE.md
Claude Code instructions for Kaademos/secure-sdlc-agents, covering secure sdlc — multi-agent orchestration, agent roster, lifecycle phases & handoffs, 1. plan and 2. design.
websec-validator AGENTS.md
Instructions for raccioly/websec-validator, covering agent instructions, project overview, project documentation (cdd), build & dev commands and docguard — documentation enforcement.
numasec AGENTS.md
AGENTS.md instructions for FrancescoStabile/numasec, covering numasec agent guide, operating rules, branches, product direction and product messaging direction.
qualys-mcp CLAUDE.md
Claude Code instructions for rijul170/qualys-mcp, covering claude.md — qualys mcp, what this is, golden rules, validate and reference material.
qualys-mcp AGENTS.md
AGENTS.md instructions for rijul170/qualys-mcp: See CLAUDE.md for full guidance and docs/MODULEBUILDGUIDE.md for the module contract.