audit

Audit repositories for secret handling, webview boundaries, persistence, and logging redaction.

6|1|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/enyst/OpenHands-Tab --skill audit-enyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/enyst/OpenHands-Tab/tree/main/.openhands/skills/audit
Command: npx skills add https://github.com/enyst/OpenHands-Tab --skill audit-enyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of conducting security audits on code repositories, identifying potential vulnerabilities and ensuring best practices are followed.

Core Features & Use Cases

  • Automated Security Audits: Runs a repeatable checklist against a repository to identify risks.
  • Threat Modeling: Assesses risks specific to the repository's context (e.g., VS Code extensions).
  • Use Case: Before merging a new feature, run the /audit command to ensure no secrets are accidentally exposed in logs or configuration files.

Quick Start

Run a security audit on the current repository using the /audit command.

Frequently Asked Questions about audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security audit on my repository?

To run a security audit, execute the /audit command against your repository. This triggers an automated checklist that analyzes provider API key names, extension-managed secret keys, and confirms secrets are not persisted in VS Code settings.

What does an automated code audit check for?

An automated code audit checks for secret handling vulnerabilities, webview and host boundary security, persistence configurations, and logging redaction. It assesses repository-specific risks to ensure secrets are not exposed in logs or configuration files.

Can I use this audit skill for VS Code extension threat modeling?

Yes, this audit skill performs threat modeling specifically tailored for VS Code extensions. It assesses context-specific risks by verifying webview boundaries are secure and profile persistence excludes managed secrets.

How do I ensure secrets are not exposed in webview boundaries and logs?

To ensure secrets are not exposed, run an audit to verify logging is properly redacted and webview boundaries are secure. The audit confirms provider API keys and extension-managed secrets are excluded from VS Code settings persistence.

What is the best way to check if secrets are persisted in VS Code settings?

The best way to check if secrets are persisted in VS Code settings is to run an automated repository audit. It analyzes provider API key names and extension-managed secret keys to confirm they are not accidentally saved in configuration files.