Use when reviewing code for security vulnerabilities, hardening an application, or deriving security requirements from OWASP/ASVS guidance.
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
# Security Audit
Perform a structured security audit of code, configuration, and architecture. Identify vulnerabilities, rank them by severity, and recommend concrete fixes grounded in OWASP standards, framework-specific best practices, and DevSecOps controls.
This is a **read-only analysis**. Do not modify code — audit, then report.
## Usage
```bash
/security-audit [scope]
```
- With no argument, audit the current branch's diff against the default branch.
- With a path or module name, audit that scope.
- Use `full` to audit the whole repository for systemic issues.
## Knowledge Base
The audit draws on five reference areas. Load the relevant reference file when a finding needs grounding or when you need detailed requirements for a topic:
| Area | Reference | When to load |
| --- | --- | --- |
| OWASP Top 10 | `reference/owasp-top-10.md` | Classifying a finding against the major vulnerability categories (2021 + 2025) |
| OWASP ASVS | `reference/owasp-asvs.md` | Deriving concrete security requirements or building a verification checklist |
…
The line at the top of this page pins the label git:20260814.d1987f5, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (11660 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
GitHub
jellydn/my-ai-tools · 128 stars · license MIT · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_umsm32pmbqd7jzsu
GET https://markdownregistry.com/api/v1/resolve?ref=jellydn/my-ai-tools/security-audit
GET https://markdownregistry.com/api/v1/blob/a5965534f4c1d3b63953be884c02d1684d306740e5c8ef7500826fa35c0fdf80
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.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/accountable-engineering/SKILL.md · Use explicit human checkpoints for architecture, security, rollout, or operational decisions.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/babysit-pr/SKILL.md · Use when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/blindspot-pass/SKILL.md · Inspect history and architecture for hidden constraints before risky cross-cutting changes.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/capability-experiments/SKILL.md · Build an interactive report or experiment when the user asks to explore model capabilities.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/code-quality-review/SKILL.md · Audit a diff for structural maintainability and unnecessary complexity.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/code-review/SKILL.md · Review a branch, PR, or worktree diff for repository conventions and stated intent.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/codemap/SKILL.md · Create a seven-document architecture map when the user asks to map a codebase.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/commit-atomic/SKILL.md · Group staged changes into atomic commits with commitizen convention
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/context-discovery/SKILL.md · Use MCP tools to trace behavior that spans multiple modules or history sources.
maxmiksa/auto-company · .claude/skills/security-audit/SKILL.md · Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing…
cowork-os/cowork-os · resources/skills/security-audit/SKILL.md · Answer security questions about code, review a file or change for vulnerabilities, or run a full multi-agent audit of a…
josstei/maestro-orchestrate · plugins/maestro/skills/security-audit/SKILL.md · Run a Maestro-style security assessment for authentication, authorization, data exposure, secret handling, and…
