.claude/skills/forensic-auditRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Three-phase read-only forensic audit of a codebase. Use when the user invokes `/forensic-audit`, asks to run a "forensic audit", "forensic audit pipeline", "multi-pass audit", "security audit", "vulnerability scan", "security check", or "code vulnerability scan".
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/forensic-auditRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/forensic-auditRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/forensic-auditRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @bergschloss/forensic-auditclawhub inspect @bergschloss/forensic-audit --version 0.1.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:64ad8b934ca4ebab8cc54de6ba5a8b3c4949fa1840fee22553525358bf954e1dimages/logo.pngREADME.mdskill-card.mdSKILL.mdtasks-forensic-example.mdforensic-audit v0.1.0 - Initial release of the forensic-audit skill for three-phase, read-only audits of codebases. - Automatically handles pre-flight setup: output directories, repo context capture, quick scans, and directory snapshots. - Phase 1: Deep security and privacy analysis with detailed severity breakdowns and executive summaries. - Phase 2: Independent database integrity and performance audit, including concurrency, index, query, and pooling checks. - Audit phases generate timestamped, persistent markdown reports with strict read-only enforcement (no repo modifications). - Triggered by explicit audit requests or via related security/vulnerability keywords.