agentsclimarketplace

Damage control

Skill webdevtodayjason/dev-kit/plugins/dev-kit/skills/damage-control

Portable Claude Code dev workflow — skills, commands, agents, security hooks, and a CLAUDE.md template. One-install onboarding; ships zero credentials.

Install
npx -y skills add webdevtodayjason/dev-kit --skill damage-control

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Install, configure, and manage the Claude Code Damage Control security hooks system. Use when user mentions damage control, security hooks, protected paths, blocked commands, install security, or modify protection settings.

SKILL.md

8.7 KB, as published. Nobody here has run it

Damage Control Skill

Defense-in-depth protection system for Claude Code. Blocks dangerous commands and protects sensitive files via PreToolUse hooks.

Overview

This skill helps users deploy and manage the Damage Control security system, which provides:

  • Command Pattern Blocking: Blocks dangerous bash commands (rm -rf, git reset --hard, etc.)
  • Ask Patterns: Triggers confirmation dialog for risky-but-valid operations (ask: true)
  • Path Protection Levels:
    • zeroAccessPaths - No access at all (secrets/credentials)
    • readOnlyPaths - Read allowed, modifications blocked
    • noDeletePaths - All operations except delete

Skill Structure

.claude/skills/damage-control/
├── SKILL.md                     # This file
├── patterns.yaml                # Shared security patterns (single source of truth)
├── cookbook/
│   ├── install_damage_control_ag_workflow.md
│   ├── modify_damage_control_ag_workflow.md
│   ├── manual_control_damage_control_ag_workflow.md
│   ├── list_damage_controls.md
│   ├── test_damage_control.md
│   └── build_for_windows.md
├── hooks/
│   ├── damage-control-python/   # Python/UV implementation
│   │   ├── bash-tool-damage-control.py
│   │   ├── edit-tool-damage-control.py
│   │   ├── write-tool-damage-control.py
│   │   ├── python-settings.json
│   │   └── test-damage-control.py
│   └── damage-control-typescript/  # Bun/TypeScript implementation
│       ├── bash-tool-damage-control.ts
│       ├── edit-tool-damage-control.ts
│       ├── write-tool-damage-control.ts
│       ├── typescript-settings.json
│       └── test-damage-control.ts
└── test-prompts/                # Test prompts for validation
    ├── sentient_v1.md
    ├── sentient_v2.md
    ├── sentient_v3.md
    └── sentient_v4.md

After Installation

The install workflow copies hooks and creates settings based on the chosen level:

Global Hooks

~/.claude/
├── settings.json                      # Hook configuration
└── hooks/
    └── damage-control/
        ├── patterns.yaml
        ├── bash-tool-damage-control.py (or .ts)
        ├── edit-tool-damage-control.py
        └── write-tool-damage-control.py

Project Hooks

<agents current working directory>/
└── .claude/
    ├── settings.json                  # Hook configuration (shared)
    └── hooks/
        └── damage-control/
            ├── patterns.yaml
            ├── bash-tool-damage-control.py (or .ts)
            ├── edit-tool-damage-control.py
            └── write-tool-damage-control.py

Project Personal Hooks

<agents current working directory>/
└── .claude/
    ├── settings.local.json            # Personal overrides (gitignored)
    └── hooks/
        └── damage-control/
            ├── patterns.yaml
            ├── bash-tool-damage-control.py (or .ts)
            ├── edit-tool-damage-control.py
            └── write-tool-damage-control.py

Cookbook

This section defines the decision tree for handling user requests. Based on what the user says, read and execute the appropriate workflow prompt.

Installation Pathway

Trigger phrases: "install damage control", "setup security hooks", "deploy damage control", "add protection"

Workflow: Read and execute cookbook/install_damage_control_ag_workflow.md

Modification Pathway

Trigger phrases: "help me modify damage control", "update protection", "change blocked paths", "add restricted directory"

Workflow: Read and execute cookbook/modify_damage_control_ag_workflow.md

Manual Control Pathway

Trigger phrases: "how do I manually update", "explain damage control config", "show me the settings"

Workflow: Read and execute cookbook/manual_control_damage_control_ag_workflow.md

Testing Pathway

Trigger phrases: - "test damage control", - "run damage control tests", - "verify hooks are working" - "damage control test this command <x>" - "damage control test this read to this path <x>" - "damage control test this write to this path <x>" - "damage control test this delete to this path <x>" - "damage control test this run this command <x>"

Workflow: Read and execute cookbook/test_damage_control.md

What it does:

  • Reads patterns.yaml to get all configured patterns and paths
  • Tests PreToolUse hooks (bash, edit, write) with exit code validation
  • Tests ask patterns with JSON output validation
  • Reports pass/fail for each test case
  • Provides summary of all results

Windows Build Pathway

Trigger phrases: "build for windows", "add windows patterns", "convert to windows", "windows damage control"

Workflow: Read and execute cookbook/build_for_windows.md

What it does:

  • Checks for existing installation
  • Adds Windows PowerShell and cmd patterns alongside Unix patterns
  • Creates cross-platform patterns.yaml that works on both systems

Direct Command Pathway

Trigger phrases: "update global read only paths to include X", "add /secret to zero access paths", "block command Y"

Action: Execute immediately without prompts - the user knows the system.

Examples:

  • "add ~/.credentials to zero access paths" → Edit patterns.yaml directly
  • "block the command 'npm publish'" → Add pattern to bashToolPatterns
  • "make /var/log read only" → Add to readOnlyPaths

Quick Reference

Settings File Locations

LevelPathScope
Global~/.claude/settings.jsonAll projects
Project.claude/settings.jsonCurrent project (shared)
Project Personal.claude/settings.local.jsonCurrent project (personal)

Path Protection Levels

TypeReadWriteEditDeleteUse Case
zeroAccessPathsNoNoNoNoSecrets, credentials
readOnlyPathsYesNoNoNoSystem configs, history
noDeletePathsYesYesYesNoImportant project files

Runtime Requirements

ImplementationRuntimeInstall Command
PythonUV (Astral)curl -LsSf https://astral.sh/uv/install.sh | sh
TypeScriptBuncurl -fsSL https://bun.sh/install | bash && bun add yaml

Exit Codes

CodeMeaning
0Allow operation
0Ask (JSON output triggers dialog)
2Block operation

Testing

Use the test prompts in test-prompts/ to validate the hooks:

  • sentient_v1.md - Tests rm -rf blocking (bashToolPatterns)
  • sentient_v2.md - Tests find -delete blocking (noDeletePaths)
  • sentient_v3.md - Tests ask patterns (SQL DELETE with ID)
  • sentient_v4.md - Tests simple command blocking

Run a test:

/project:test-prompts/sentient_v1

Related Files

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.