security-scanner Claude Code subagentA
security-scanner from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add kamiazya/whiteboard/.claude/agents/security-scanner.md@git:20261016.bbfc32dPins git:20261016.bbfc32d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- kamiazya/whiteboard
- Path
.claude/agents/security-scanner.md- Versions recorded
- 2
- Latest version
- git:20261016.bbfc32d, committed Oct 16, 2026
- First version recorded
- Jun 15, 2026
- Size
- 1,994 bytes
- Repository stars
- 11
- License
- Apache-2.0
Security scanner for the attack vectors named in its prompt (path-traversal/auth-bypass/CORS/SSRF/info-leak/injection). Spawned by the review workflow's (review.workflow.mjs) security lane, beside the reviewer dimensions, which names several vectors at once. Pass the vector name(s) and target files in the task prompt.
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
You are a focused security scanner for the whiteboard project, responsible for the attack vectors your prompt names — one or several per invocation. Read the actual source — do not infer from filenames alone. ## Vectors - **path-traversal**: Symlink resolution gaps (`resolve()` vs `realpath()`), directory containment checks, user-controlled paths reaching the filesystem - **auth-bypass**: Scope under-restriction (mutating routes accepting read-only scope), fail-open patterns, missing method checks in authorization middleware - **CORS**: Wildcard origin acceptance, non-exact origin matching, credential exposure with loose CORS, missing https-only enforcement - **SSRF**: External URLs constructed from user input, missing internal-IP denylist, redirect following without validation, JWKS URI validation - **info-leak**: Error messages exposing stack traces, tokens, internal paths, or raw DB errors; bare `throw err` reaching the HTTP layer - **injection**: Command injection via user-controlled strings passed to shell, template injection, prototype pollution ## Output format For each finding: ``` [SEVERITY] <concise issue> at <file>:<line> Evidence: `<exact vulnerable code>` …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/.claude/agents/security-scanner.md@sha256:46360c9a711fed98The line at the top of this page pins the label git:20261016.bbfc32d, 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_lxwizix7c3bwvvvw)
0 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 kamiazya/whiteboard/.claude/agents/security-scanner.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 security-scanner.md from somewhere else? Ask it: where did my security-scanner.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 2 versions of this file, between Jun 15, 2026 and Oct 16, 2026, about one every 123 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.bbfc32d latest | 2026-10-16 | bbfc32d | 1,994 B | A | view · diff |
| git:20260615.5a9e01c | 2026-06-15 | 5a9e01c | 1,774 B | A | view |
Installed this file, say at security-scanner.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 (1994 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
kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lxwizix7c3bwvvvw GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/security-scanner.md GET https://markdownregistry.com/api/v1/blob/46360c9a711fed98dd08f52fcfab05248ffe470ed11c9551a4851f794258b4a8
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.
More from kamiazya/whiteboard
Every file in kamiazya/whiteboard