toolguard-security-audit

Audit toolguard permission configurations for dangerous allow rules and takeover-mode misconfigurations.

Updated May 3, 2017
One-click install
npx skills add https://github.com/arnonmoscona/dot_files --skill toolguard-security-audit-arnonmoscona
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toolguard-security-audit
Source: https://github.com/arnonmoscona/dot_files/tree/main/wsl/.claude/skills/toolguard-security-audit
Command: npx skills add https://github.com/arnonmoscona/dot_files --skill toolguard-security-audit-arnonmoscona

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Toolguard and Claude Code permission configurations can silently accumulate over-broad allow rules, broken takeover-mode setups, and unregistered hooks that leave a project ungoverned. This Skill audits the entire config hierarchy and flags those risks before they become security holes. ## Core Features & Use Cases - Deterministic analysis: Runs the tested toolguard-audit Python analyzer to mechanically flag dangerous allow patterns and takeover-mode invariant violations with CRITICAL/HIGH/MEDIUM/LOW severities. - Optional AI-assisted assessment: On user approval, performs a judgement-based review of the consolidated config context to catch combinational escapes, over-broad globs, and missing hardening that deterministic detectors cannot see. - Structured remediation proposals: Emits machine-appliable EditProposal fixes alongside human-readable remediation text, while remaining strictly read-only and never editing config files. - Use Case: At the start of a session, ask for a security check of your project's toolguard setup to discover that a blanket Bash(curl:*) allow or an unregistered hook is silently disabling governance. ## Quick Start Ask the assistant to run a security audit of the toolguard permission configuration in the current project and report any risky allow rules.

Frequently Asked Questions about toolguard-security-audit

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

FAQPage Schema
How do I audit my toolguard permission configuration for security risks?

Invoke the skill from the project you want to audit; it runs `toolguard-audit --format json`, which discovers the full config hierarchy upward from that directory. Findings are grouped by severity with remediation suggestions, and no config files are modified.

What does the toolguard security audit check for?

It flags dangerous allow patterns such as arbitrary execution rules, plus takeover-mode invariant violations like an unregistered hook. An optional AI-assisted pass also catches combinational escapes, over-broad globs, and missing deny hardening.

Does the security audit modify my toolguard or settings.json config?

No, the audit is strictly read-only. It reports findings and proposes concrete fixes, including structured EditProposal objects, but applying any change is a separate explicit user decision handled by the maintenance tooling.

Why is toolguard-audit not found when running the audit?

The console script is installed by `uv tool install toolguard`; a missing command means the install is absent, outdated, or partial. Run `uv tool install toolguard` or `uv tool upgrade toolguard`, and do not substitute other invocation forms outside maintainer dev mode.

What is the difference between the deterministic and AI-assisted audit passes?

The deterministic pass is a tested Python analyzer whose findings and severities are authoritative and repeatable. The AI-assisted pass is opt-in, judgement-based, may include false positives, and labels each finding with an ordinal confidence level in a separate report section.

What does a #NOSECURITY comment do on a toolguard rule?

A `#NOSECURITY[: reason]` comment marks a rule as an acknowledged, intentional risk. The finding still appears in the report flagged as acknowledged and sorted last, but it is not re-raised as a headline or proposed for removal.