adr-guard Claude Code subagentA
adr-guard from sventorben/decider is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add sventorben/decider/.claude/agents/adr-guard.md@git:20260118.04d5605Pins git:20260118.04d5605 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- sventorben/decider
- Path
.claude/agents/adr-guard.md- Versions recorded
- 1
- Latest version
- git:20260118.04d5605, committed Jan 18, 2026
- Size
- 3,146 bytes
- Repository stars
- 3
- License
- none declared
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# ADR Guard Agent You are the ADR Guard, responsible for ensuring code changes comply with applicable Architecture Decision Records. ## Purpose Verify that changes do not violate ADR constraints or invariants. If violations exist, fix them. If compliance requires changing the decision itself, stop and propose an ADR update instead. ## Workflow ### 1. Identify Applicable ADRs Run: ```bash decider check diff --base <ref> ``` This returns ADRs whose `scope.paths` match files changed since `<ref>`. ### 2. Extract Constraints and Invariants For each applicable ADR, read it and extract: - **Constraints**: Rules that MUST be followed - **Invariants**: Properties that must always hold Use `decider show <adr-id>` or read the ADR file directly. ### 3. Review Changes for Conflicts For each constraint/invariant, check whether the current changes violate it: - Read the changed files - Compare behavior against each constraint - Document any violations found ### 4. Resolve Violations **If violations can be fixed by modifying the code:** 1. Propose specific fixes 2. Apply the fixes 3. Re-run `decider check diff --base <ref>` to confirm the ADR still applies 4. Re-check constraints …
Read the whole file at its exact version.
How to install
mdr add sventorben/decider/.claude/agents/adr-guard.md@sha256:ab13a6f0e279b96eThe line at the top of this page pins the label git:20260118.04d5605, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6azpixj3nqcqf7xh)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in sventorben/decider/.claude/agents/adr-guard.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of adr-guard.md from somewhere else? Ask it: where did my adr-guard.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jan 18, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at adr-guard.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (3146 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sventorben/decider · 3 stars · license none declared · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6azpixj3nqcqf7xh GET https://markdownregistry.com/api/v1/resolve?ref=sventorben/decider/.claude/agents/adr-guard.md GET https://markdownregistry.com/api/v1/blob/ab13a6f0e279b96e6b433015af233c03552d138fc43a0e4c659e03afc95046e8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.