harness-audit

Audit Claude Code hooks, plugins, MCP servers, and settings for security risks.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill harness-audit-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-audit
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/harness-audit
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill harness-audit-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The Claude Code harness is a privileged execution environment where hooks run arbitrary code, third-party plugins inject instructions into context, and settings can redirect the model or widen auto-approval. This Skill systematically audits that attack surface to detect malicious hooks, supply-chain risks, and misconfigurations before they cause compromise. ## Core Features & Use Cases - Hook and Transcript Audit: Scans registered hooks for network egress, transcript-read-plus-exfiltration pairings, and obfuscated execution, with taint-tracing and CONFIRMED/TRACED/CANDIDATE severity tiers. - Supply-Chain and Settings Review: Detects hidden unicode in skills and plugin caches, unpinned plugin versions, dangerous settings like ANTHROPIC_BASE_URL redirects or enableAllProjectMcpServers, and over-broad permission allow-lists. - Use Case: After installing a new plugin marketplace or MCP server, run the audit to verify no hook exfiltrates transcripts, no plugin contains prompt-injection payloads, and your Claude version is above the known-CVE floor, with findings filed as [SECURITY] TODOs. ## Quick Start Ask the AI to audit your Claude setup by saying: run a harness audit on my Claude Code hooks, plugins, and settings and report any security findings.

Frequently Asked Questions about harness-audit

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

FAQPage Schema
How do I audit Claude Code hooks for malicious code?▼

Scan hook files for network egress patterns like curl, wget, or requests, then taint-trace each hit to confirm data flow. A hook that reads transcripts and has network reach in the same file is a critical finding; pattern matches inside guard regexes are expected self-hits.

What security risks do Claude Code plugins and MCP servers pose?▼

Third-party plugins load instructions into every session as a prompt-injection supply chain, and MCP servers add tool supply-chain risk with network reach. The audit checks for hidden unicode payloads, unpinned versions, and unused plugins that are pure attack surface.

Can Claude Code settings redirect the model or leak API keys?▼

Yes. ANTHROPIC_BASE_URL in settings.json redirects the model itself, and apiKeyHelper can leak credentials. The audit flags these as critical unless deliberately configured, and also checks enableAllProjectMcpServers and over-broad permission allow-lists.

Does the harness audit modify my system or settings?▼

No, the audit is strictly read-only. Findings are filed as [SECURITY]-tagged TODO items in the dotfiles TODOS.md file, and remediation is handled as a separate task after user confirmation.

Why does the audit check for hidden unicode in skill files?▼

Invisible unicode characters like zero-width spaces and directional overrides can plant payloads that are invisible during code review. Since plugin skills load into context, hidden unicode is a prompt-injection vector that must be scanned with escaped character classes.