destructive-command-guard
Blocks dangerous commands before execution via a Rust-based Claude Code hook. Use when configuring agent safety guards, setting up destructive command blocking, or auditing CLI protection rules. Use for git reset protection, rm -rf interception, force-push blocking, pack-based command filtering, and PreToolUse hook safety.
What this skill does
# Destructive Command Guard A high-performance Claude Code hook that intercepts and blocks destructive commands before they execute. Written in Rust with SIMD-accelerated filtering via the `memchr` crate and Aho-Corasick multi-pattern matching for sub-millisecond latency. Assumes agents are well-intentioned but fallible. ## Overview DCG uses a whitelist-first architecture: safe patterns are checked before destructive patterns, and unrecognized commands are allowed by default (fail-safe). This ensures legitimate workflows are never broken while known dangerous patterns are always blocked. DCG runs as a `PreToolUse` hook in Claude Code, receiving JSON on stdin for each Bash tool invocation and returning exit code `0` (allow) or `2` (block). It only inspects direct Bash tool invocations, not contents of shell scripts. The processing pipeline has four stages: JSON parsing, command normalization (strips absolute paths like `/usr/bin/git`), SIMD quick-reject filter (skips regex for commands without `git` or `rm`), and pattern matching. The `memchr` crate provides hardware-accelerated substring search (SSE2/AVX2 on x86_64, NEON on ARM), while Aho-Corasick handles multi-pattern matching in O(n) time regardless of pattern count. DCG supports 49+ modular security packs organized by category (git, filesystem, databases, containers, Kubernetes, cloud providers, infrastructure tools). Core packs (`core.git`, `core.filesystem`) are always enabled; additional packs are configured via `~/.config/dcg/config.toml` or the `DCG_PACKS` environment variable. The `dcg scan` subcommand can also audit files for destructive command contexts, suitable for CI integration. DCG is not published on crates.io; it is installed from GitHub via `cargo +nightly install` or prebuilt binaries for Linux, macOS, and Windows WSL. The threat model assumes agents are well-intentioned but fallible; DCG catches honest mistakes, not adversarial attacks. ## Quick Reference | Category | Blocked Commands | | ---------------- | ---------------------------------------------------------------------------------- | | Uncommitted work | `git reset --hard`, `git checkout -- <file>`, `git restore <file>`, `git clean -f` | | Remote history | `git push --force` / `-f`, `git branch -D` | | Stashed work | `git stash drop`, `git stash clear` | | Filesystem | `rm -rf` (outside `/tmp`, `/var/tmp`, `$TMPDIR`) | | Category | Allowed Commands | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Safe git | `git status`, `git log`, `git diff`, `git add`, `git commit`, `git push`, `git pull`, `git fetch`, `git branch -d`, `git stash`, `git stash pop` | | Safe patterns | `git checkout -b`, `git restore --staged`, `git clean -n`, `git push --force-with-lease` | | Temp dirs | `rm -rf /tmp/*`, `rm -rf $TMPDIR/*` | | Setting | Value | | -------------------- | ------------------------------------ | | Exit code (safe) | `0` | | Exit code (blocked) | `2` | | Default behavior | Allow (fail-safe) | | Pattern priority | Safe checked first, then destructive | | Safe patterns | 34 | | Destructive patterns | 16 | | Pack Category | Examples | | -------------- | --------------------------------------------------------------- | | Core (default) | `core.git`, `core.filesystem` | | Database | `database.postgresql`, `database.mysql`, `database.mongodb` | | Containers | `containers.docker`, `containers.compose`, `containers.podman` | | Kubernetes | `kubernetes.kubectl`, `kubernetes.helm`, `kubernetes.kustomize` | | Cloud | `cloud.aws`, `cloud.gcp`, `cloud.azure` | | Infrastructure | `infrastructure.terraform`, `infrastructure.ansible` | | System | `system.disk`, `system.permissions`, `system.services` | | Other | `strict_git`, `package_managers` | | Environment Variable | Purpose | | -------------------- | ---------------------------------- | | `DCG_PACKS` | Enable packs (comma-separated) | | `DCG_DISABLE` | Disable specific packs | | `DCG_VERBOSE` | Verbose output | | `DCG_BYPASS` | Bypass DCG entirely (escape hatch) | | `DCG_COLOR` | Color mode (auto, always, never) | | Installation Method | Command | | ------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Quick install | `curl -fsSL ".../install.sh" \| bash -s -- --easy-mode` | | From source | `cargo +nightly install --git https://github.com/Dicklesworthstone/destructive_command_guard destructive_command_guard` | | Prebuilt binaries | Linux x86_64, Linux ARM64, macOS Intel, macOS Apple Silicon, Windows WSL | | Processing Stage | Description | | ----------------- | ------------------------------------------------------------- | | JSON parsing | Reads `PreToolUse` hook input, allows non-Bash tools | | Normalization | Strips absolute paths (`/usr/bin/git` becomes `git`) | | SIMD quick-reject | `memchr` substring search skips regex for irrelevant commands | | Pattern matching | Safe patterns first, then destructive, default allow | ## Common Mistakes | Mistake | Correct Pattern | | ---------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Forgetting to restart Claude Code after adding the hook | Always restart Claude Code after modifying `~/.claude/settings.json` | | Using `DCG_BYPASS=1` permanently in shell profile | Only set bypass temporarily for a single command, then remove it | | Assuming DCG inspects commands inside scripts | DCG only inspects direct Bash tool invocations, not contents of `./deploy.sh` | | Blocking `git branch -d` (lowercase) thinking it is destructive | Lowercase `-d` is safe (merge-checked); only uppercase `-D` force-deletes | | Not enabling database or cloud packs for production environments | Configure relevant packs in `~/.config/dcg/config.toml` for your stack | | Expecting DCG to stop malicious actors | DCG catches honest mistakes; determined users can always bypass the hook | | Running `cargo install` without nightly toolchain | DCG requires Rust nightly (edition 2024); use `cargo +nightly install` | ## Delegation - **Audit which destructive commands an agent session has attempted**: Use `Explore` agent - **Set up DCG with custom packs for a new project e
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.