fix-nested-code-fences — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited fix-nested-code-fences (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
When a code block contains inner triple-backtick fences, replace the outer fence with ~~~ — the minimum change that fixes rendering without altering any content.
Don't: change inner fences — only the outer fence needs replacing. Don't apply this to tilde fences that are already correct.
When markdown is generated or written that contains code block examples inside other code blocks, the inner fences terminate the outer block early, breaking rendered output. Common in: skill templates, documentation generators, README examples, any file where markdown is shown inside markdown.
Replace the outer fence with ~~~ when the block contains inner ` fences. Inner fences stay as-is.
Before:
VAR=valueAfter: ~~~~ ~~~markdown
VAR=value~~~ ~~~~
` fences~~~~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.