Home / wst2002 / claude-code-skills · GitHub

security-audit SKILL.md skillA

security-audit from wst2002/claude-code-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add wst2002/claude-code-skills/security-audit@git:20261016.55bd98a

Pins git:20261016.55bd98a in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: wst2002/claude-code-skills
Path: skills/security-audit/SKILL.md
Versions recorded: 2
Latest version: git:20261016.55bd98a, committed Oct 16, 2026
First version recorded: Oct 16, 2026
Size: 3,000 bytes
Repository stars: 3
License: MIT

Use when asked to review code for security, find vulnerabilities, run an OWASP check, audit before a release, or answer "is this secure?" — any language or framework, whole repo or a single feature.

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

## Overview

Find vulnerabilities an attacker can actually reach, prove each one with code, and say exactly how to fix it. A short list of real, exploitable findings beats a long list of maybes.

## Method

1. **Scope.** Identify entry points: HTTP routes, CLI args, file uploads, message consumers, webhooks, scheduled jobs. Note the framework and auth mechanism.
2. **Map trust boundaries.** For each entry point, follow untrusted input to where it is used (query, shell, file path, HTML, redirect, deserializer, template).
3. **Sweep by class.** Search systematically with the patterns in [checklist.md](checklist.md). Do not stop at the first hit per class.
4. **Verify every candidate** before reporting:
   - Is the input attacker-controlled? Trace it.
   - Is there validation, escaping, parameterisation or an auth check on the path?
   - Is the code reachable in production (not a test, fixture, or dead code)?
   If any answer removes the risk, drop it or mark it Low confidence.
5. **Check configuration and dependencies:** CORS, cookies, headers, debug flags, secrets in repo, known-vulnerable versions in lockfiles.
6. **Report** using the contract below.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add wst2002/claude-code-skills/security-audit@sha256:889dd0a6466fee87

The line at the top of this page pins the label git:20261016.55bd98a, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_p6bs7m5fkkfxzlv3.svg)](https://markdownregistry.com/a/art_p6bs7m5fkkfxzlv3)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, all committed on Oct 16, 2026.

version	committed	commit	size	audit
git:20261016.55bd98a latest	2026-10-16	55bd98a	3,000 B	A	view · diff
git:20261016.c3a2cef	2026-10-16	c3a2cef	2,798 B	A	view

Audit of the latest version

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 (3000 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

wst2002/claude-code-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_p6bs7m5fkkfxzlv3
GET https://markdownregistry.com/api/v1/resolve?ref=wst2002/claude-code-skills/security-audit
GET https://markdownregistry.com/api/v1/blob/889dd0a6466fee876eb72855265555ddc368fa16392d8038791e75f9241da5a3

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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from wst2002/claude-code-skills

proof-of-done SKILL.md skill

wst2002/claude-code-skills · plugins/proof-of-done/skills/proof-of-done/SKILL.md · Use before saying work is done, fixed, or complete after changing code. Run the project's checks, show their results…