HomeBrowseUpload
โ† Back to registry
โšก
// Skill profile

ClawSec Feed ๐Ÿ“ก

name: clawsec-feed

by davida-ps ยท published 2026-03-22

ๅผ€ๅ‘ๅทฅๅ…ทๆ•ฐๆฎๅค„็†ๅŠ ๅฏ†่ดงๅธ
Total installs
0
Stars
โ˜… 0
Last updated
2026-03
// Install command
$ claw add gh:davida-ps/davida-ps-clawsec-feed
View on GitHub
// Full documentation

---

name: clawsec-feed

version: 0.0.5

description: Security advisory feed with automated NVD CVE polling for OpenClaw-related vulnerabilities. Updated daily.

homepage: https://clawsec.prompt.security

metadata: {"openclaw":{"emoji":"๐Ÿ“ก","category":"security"}}

clawdis:

emoji: "๐Ÿ“ก"

requires:

bins: [curl, jq]

---

# ClawSec Feed ๐Ÿ“ก

Security advisory feed monitoring for AI agents. Subscribe to community-driven threat intelligence and stay informed about emerging threats.

This feed is automatically updated daily with CVEs related to OpenClaw, clawdbot, and Moltbot from the NIST National Vulnerability Database (NVD).

**An open source project by [Prompt Security](https://prompt.security)**

---

Installation Options

You can get clawsec-feed in two ways:

Option A: Bundled with ClawSec Suite (Recommended)

**If you've installed clawsec-suite, you may already have this!**

ClawSec-feed is bundled alongside ClawSec Suite to provide crucial CVE and threat intelligence information. When you install the suite, if you don't already have the feed installed, it will be deployed from the bundled copy.

**Advantages:**

  • Convenient - no separate download needed
  • Standard location - installed to `~/.openclaw/skills/clawsec-feed/`
  • Preserved - if you already have feed installed, it won't be overwritten
  • Single verification - integrity checked as part of suite package
  • Option B: Standalone Installation (This Page)

    Install clawsec-feed independently without the full suite.

    **When to use standalone:**

  • You only need the advisory feed (not other suite components)
  • You want to install before installing the suite
  • You prefer explicit control over feed installation
  • **Advantages:**

  • Lighter weight installation
  • Independent from suite
  • Direct control over installation process
  • Continue below for standalone installation instructions.

    ---

    Installation Steps:

    Agents should review scripts before execution!

    # Get latest clawsec-feed release tag
    LATEST_TAG=$(curl -sSL https://api.github.com/repos/prompt-security/ClawSec/releases | \
      jq -r '[.[] | select(.tag_name | startswith("clawsec-feed-v"))][0].tag_name')
    
    # Download SKILL.md from latest release
    SKILL_URL="https://github.com/prompt-security/clawsec/releases/download/$LATEST_TAG/SKILL.md"
    curl -sSL --fail --show-error "$SKILL_URL"

    Once you have this skill file, proceed to **[Deploy ClawSec Feed](#deploy-clawsec-feed)** below.

    ---

    Deploy ClawSec Feed

    Installation steps:

    Step 1: Create skill directory and save this file

    mkdir -p ~/.openclaw/skills/clawsec-feed
    # Save this SKILL.md as SKILL.md in the directory above

    Step 2: Install skill files

    # Get latest release tag with retry logic
    LATEST_TAG=$(curl -sSL --retry 3 --retry-delay 1 \
      https://api.github.com/repos/prompt-security/ClawSec/releases | \
      jq -r '[.[] | select(.tag_name | startswith("clawsec-feed-v"))][0].tag_name')
    
    BASE_URL="https://github.com/prompt-security/clawsec/releases/download/$LATEST_TAG"
    INSTALL_DIR="${CLAWSEC_INSTALL_DIR:-$HOME/.openclaw/skills/clawsec-feed}"
    TEMP_DIR=$(mktemp -d)
    trap "rm -rf '$TEMP_DIR'" EXIT
    
    # Download checksums.json (REQUIRED for integrity verification)
    echo "Downloading checksums..."
    if ! curl -sSL --fail --show-error --retry 3 --retry-delay 1 \
         "$BASE_URL/checksums.json" -o "$TEMP_DIR/checksums.json"; then
      echo "ERROR: Failed to download checksums.json"
      exit 1
    fi
    
    # Validate checksums.json structure
    if ! jq -e '.skill and .version and .files' "$TEMP_DIR/checksums.json" >/dev/null 2>&1; then
      echo "ERROR: Invalid checksums.json structure"
      exit 1
    fi
    
    # PRIMARY: Try .skill artifact
    echo "Attempting .skill artifact installation..."
    if curl -sSL --fail --show-error --retry 3 --retry-delay 1 \
       "$BASE_URL/clawsec-feed.skill" -o "$TEMP_DIR/clawsec-feed.skill" 2>/dev/null; then
    
      # Security: Check artifact size (prevent DoS)
      ARTIFACT_SIZE=$(stat -c%s "$TEMP_DIR/clawsec-feed.skill" 2>/dev/null || stat -f%z "$TEMP_DIR/clawsec-feed.skill")
      MAX_SIZE=$((50 * 1024 * 1024))  # 50MB
    
      if [ "$ARTIFACT_SIZE" -gt "$MAX_SIZE" ]; then
        echo "WARNING: Artifact too large ($(( ARTIFACT_SIZE / 1024 / 1024 ))MB), falling back to individual files"
      else
        echo "Extracting artifact ($(( ARTIFACT_SIZE / 1024 ))KB)..."
    
        # Security: Check for path traversal before extraction
        if unzip -l "$TEMP_DIR/clawsec-feed.skill" | grep -qE '\.\./|^/|~/'; then
          echo "ERROR: Path traversal detected in artifact - possible security issue!"
          exit 1
        fi
    
        # Security: Check file count (prevent zip bomb)
        FILE_COUNT=$(unzip -l "$TEMP_DIR/clawsec-feed.skill" | grep -c "^[[:space:]]*[0-9]" || echo 0)
        if [ "$FILE_COUNT" -gt 100 ]; then
          echo "ERROR: Artifact contains too many files ($FILE_COUNT) - possible zip bomb"
          exit 1
        fi
    
        # Extract to temp directory
        unzip -q "$TEMP_DIR/clawsec-feed.skill" -d "$TEMP_DIR/extracted"
    
        # Verify skill.json exists
        if [ ! -f "$TEMP_DIR/extracted/clawsec-feed/skill.json" ]; then
          echo "ERROR: skill.json not found in artifact"
          exit 1
        fi
    
        # Verify checksums for all extracted files
        echo "Verifying checksums..."
        CHECKSUM_FAILED=0
        for file in $(jq -r '.files | keys[]' "$TEMP_DIR/checksums.json"); do
          EXPECTED=$(jq -r --arg f "$file" '.files[$f].sha256' "$TEMP_DIR/checksums.json")
          FILE_PATH=$(jq -r --arg f "$file" '.files[$f].path' "$TEMP_DIR/checksums.json")
    
          # Try nested path first, then flat filename
          if [ -f "$TEMP_DIR/extracted/clawsec-feed/$FILE_PATH" ]; then
            ACTUAL=$(shasum -a 256 "$TEMP_DIR/extracted/clawsec-feed/$FILE_PATH" | cut -d' ' -f1)
          elif [ -f "$TEMP_DIR/extracted/clawsec-feed/$file" ]; then
            ACTUAL=$(shasum -a 256 "$TEMP_DIR/extracted/clawsec-feed/$file" | cut -d' ' -f1)
          else
            echo "  โœ— $file (not found in artifact)"
            CHECKSUM_FAILED=1
            continue
          fi
    
          if [ "$EXPECTED" != "$ACTUAL" ]; then
            echo "  โœ— $file (checksum mismatch)"
            CHECKSUM_FAILED=1
          else
            echo "  โœ“ $file"
          fi
        done
    
        if [ "$CHECKSUM_FAILED" -eq 0 ]; then
          # Validate feed.json structure (skill-specific)
          if [ -f "$TEMP_DIR/extracted/clawsec-feed/advisories/feed.json" ]; then
            FEED_FILE="$TEMP_DIR/extracted/clawsec-feed/advisories/feed.json"
          elif [ -f "$TEMP_DIR/extracted/clawsec-feed/feed.json" ]; then
            FEED_FILE="$TEMP_DIR/extracted/clawsec-feed/feed.json"
          else
            echo "ERROR: feed.json not found in artifact"
            exit 1
          fi
    
          if ! jq -e '.version and .advisories' "$FEED_FILE" >/dev/null 2>&1; then
            echo "ERROR: feed.json missing required fields (version, advisories)"
            exit 1
          fi
    
          # SUCCESS: Install from artifact
          echo "Installing from artifact..."
          mkdir -p "$INSTALL_DIR"
          cp -r "$TEMP_DIR/extracted/clawsec-feed"/* "$INSTALL_DIR/"
          chmod 600 "$INSTALL_DIR/skill.json"
          find "$INSTALL_DIR" -type f ! -name "skill.json" -exec chmod 644 {} \;
          echo "SUCCESS: Skill installed from .skill artifact"
          exit 0
        else
          echo "WARNING: Checksum verification failed, falling back to individual files"
        fi
      fi
    fi
    
    # FALLBACK: Download individual files
    echo "Downloading individual files from checksums.json manifest..."
    mkdir -p "$TEMP_DIR/downloads"
    
    DOWNLOAD_FAILED=0
    for file in $(jq -r '.files | keys[]' "$TEMP_DIR/checksums.json"); do
      FILE_URL=$(jq -r --arg f "$file" '.files[$f].url' "$TEMP_DIR/checksums.json")
      EXPECTED=$(jq -r --arg f "$file" '.files[$f].sha256' "$TEMP_DIR/checksums.json")
    
      echo "Downloading: $file"
      if ! curl -sSL --fail --show-error --retry 3 --retry-delay 1 \
           "$FILE_URL" -o "$TEMP_DIR/downloads/$file"; then
        echo "ERROR: Failed to download $file"
        DOWNLOAD_FAILED=1
        continue
      fi
    
      # Verify checksum immediately
      ACTUAL=$(shasum -a 256 "$TEMP_DIR/downloads/$file" | cut -d' ' -f1)
      if [ "$EXPECTED" != "$ACTUAL" ]; then
        echo "ERROR: Checksum mismatch for $file"
        DOWNLOAD_FAILED=1
      else
        echo "  โœ“ Verified: $file"
      fi
    done
    
    if [ "$DOWNLOAD_FAILED" -eq 1 ]; then
      echo "ERROR: Individual file download failed"
      exit 1
    fi
    
    # Validate JSON files structure
    if ! jq -e '.name and .version' "$TEMP_DIR/downloads/skill.json" >/dev/null 2>&1; then
      echo "ERROR: skill.json missing required fields (name, version)"
      exit 1
    fi
    
    if ! jq -e '.version and .advisories' "$TEMP_DIR/downloads/feed.json" >/dev/null 2>&1; then
      echo "ERROR: feed.json missing required fields (version, advisories)"
      exit 1
    fi
    
    # Install files
    echo "Installing from individual files..."
    mkdir -p "$INSTALL_DIR"
    cp "$TEMP_DIR/downloads"/* "$INSTALL_DIR/"
    chmod 600 "$INSTALL_DIR/skill.json"
    find "$INSTALL_DIR" -type f ! -name "skill.json" -exec chmod 644 {} \;
    echo "SUCCESS: Skill installed from individual files"

    Step 3: Add to your heartbeat

    Add ClawSec Feed to your heartbeat routine:

    ## ClawSec Feed (every heartbeat)
    1. Check advisory feed for new security alerts
    2. Cross-reference with installed skills
    3. Notify user if action is required

    Step 4: Confirm deployment

    Tell your user:

    ClawSec Feed deployed successfully. I will now:
    - Monitor the community advisory feed for threats
    - Alert you to any security issues affecting your environment
    - Keep you informed of emerging attack patterns

    ---

    What ClawSec Feed Does

    Advisory Feed Monitoring

    Subscribes to the community advisory feed for:

  • **Known malicious skills/plugins** - Skills that have been identified as harmful
  • **Prompt injection patterns** - Attack patterns observed in the wild
  • **Vulnerable skill versions** - Skills with known security flaws
  • **Security best practice updates** - New recommendations for agent safety
  • When a relevant advisory is published, your agent will notify you.

    ---

    Checking the Advisory Feed

    # Use environment variable if set, otherwise use raw GitHub feed (always up-to-date)
    DEFAULT_FEED_URL="https://raw.githubusercontent.com/prompt-security/ClawSec/main/advisories/feed.json"
    FEED_URL="${CLAWSEC_FEED_URL:-$DEFAULT_FEED_URL}"
    
    # Fetch with error handling and retry logic
    curl -sSL --fail --show-error --retry 3 --retry-delay 1 "$FEED_URL"

    **Feed structure:**

    {
      "version": "1.0",
      "updated": "2026-02-02T12:00:00Z",
      "advisories": [
        {
          "id": "GA-2026-001",
          "severity": "critical",
          "type": "malicious_skill",
          "title": "Malicious data exfiltration in skill 'helper-plus'",
          "description": "Skill sends user data to external server",
          "affected": ["helper-plus@1.0.0", "helper-plus@1.0.1"],
          "action": "Remove immediately",
          "published": "2026-02-01T10:00:00Z",
          "exploitability_score": "critical",
          "exploitability_rationale": "Trivially exploitable through normal skill usage; no special conditions required. Active exploitation observed in the wild."
        }
      ]
    }

    ---

    Parsing the Feed

    Get advisory count

    # Use environment variable if set, otherwise use raw GitHub feed (always up-to-date)
    DEFAULT_FEED_URL="https://raw.githubusercontent.com/prompt-security/ClawSec/main/advisories/feed.json"
    FEED_URL="${CLAWSEC_FEED_URL:-$DEFAULT_FEED_URL}"
    
    TEMP_FEED=$(mktemp)
    trap "rm -f '$TEMP_FEED'" EXIT
    
    if ! curl -sSL --fail --show-error --retry 3 --retry-delay 1 "$FEED_URL" -o "$TEMP_FEED"; then
      echo "Error: Failed to fetch advisory feed"
      exit 1
    fi
    
    # Validate JSON before parsing
    if ! jq empty "$TEMP_FEED" 2>/dev/null; then
      echo "Error: Invalid JSON in feed"
      exit 1
    fi
    
    FEED=$(cat "$TEMP_FEED")
    
    # Get advisory count with error handling
    COUNT=$(echo "$FEED" | jq '.advisories | length')
    if [ $? -ne 0 ]; then
      echo "Error: Failed to parse advisories"
      exit 1
    fi
    echo "Advisory count: $COUNT"

    Get critical advisories

    # Parse critical advisories with jq error handling
    CRITICAL=$(echo "$FEED" | jq '.advisories[] | select(.severity == "critical")')
    if [ $? -ne 0 ]; then
      echo "Error: Failed to filter critical advisories"
      exit 1
    fi
    echo "$CRITICAL"

    Get advisories from the last 7 days

    # Use UTC timezone for consistent date handling
    WEEK_AGO=$(TZ=UTC date -v-7d +%Y-%m-%dT00:00:00Z 2>/dev/null || TZ=UTC date -d '7 days ago' +%Y-%m-%dT00:00:00Z)
    RECENT=$(echo "$FEED" | jq --arg since "$WEEK_AGO" '.advisories[] | select(.published > $since)')
    if [ $? -ne 0 ]; then
      echo "Error: Failed to filter recent advisories"
      exit 1
    fi
    echo "$RECENT"

    Filter by exploitability score

    Shared exploitability prioritization guidance is maintained in:

  • [`wiki/exploitability-scoring.md`](../../wiki/exploitability-scoring.md)
  • [`skills/clawsec-suite/SKILL.md`](../clawsec-suite/SKILL.md) ("Quick feed check")
  • Get exploitability context for an advisory

    # Show exploitability details for a specific CVE
    CVE_ID="CVE-2026-27488"
    echo "$FEED" | jq --arg cve "$CVE_ID" '.advisories[] | select(.id == $cve) | {
      id: .id,
      severity: .severity,
      exploitability_score: .exploitability_score,
      exploitability_rationale: .exploitability_rationale,
      title: .title
    }'

    Prioritize advisories by exploitability

    # Sort advisories by exploitability (critical โ†’ high โ†’ medium โ†’ low)
    # This helps agents focus on the most immediately actionable threats
    echo "$FEED" | jq '[.advisories[] | select(.exploitability_score != null)] |
      sort_by(
        if .exploitability_score == "critical" then 0
        elif .exploitability_score == "high" then 1
        elif .exploitability_score == "medium" then 2
        elif .exploitability_score == "low" then 3
        else 4 end
      )'

    ---

    Cross-Reference Installed Skills

    Check if any of your installed skills are affected by advisories:

    # List your installed skills (adjust path for your platform)
    INSTALL_DIR="${CLAWSEC_INSTALL_DIR:-$HOME/.openclaw/skills}"
    
    # Use environment variable if set, otherwise use raw GitHub feed (always up-to-date)
    DEFAULT_FEED_URL="https://raw.githubusercontent.com/prompt-security/ClawSec/main/advisories/feed.json"
    FEED_URL="${CLAWSEC_FEED_URL:-$DEFAULT_FEED_URL}"
    
    TEMP_FEED=$(mktemp)
    trap "rm -f '$TEMP_FEED'" EXIT
    
    if ! curl -sSL --fail --show-error --retry 3 --retry-delay 1 "$FEED_URL" -o "$TEMP_FEED"; then
      echo "Error: Failed to fetch advisory feed"
      exit 1
    fi
    
    # Validate and parse feed
    if ! jq empty "$TEMP_FEED" 2>/dev/null; then
      echo "Error: Invalid JSON in feed"
      exit 1
    fi
    
    FEED=$(cat "$TEMP_FEED")
    AFFECTED=$(echo "$FEED" | jq -r '.advisories[].affected[]?' 2>/dev/null | sort -u)
    if [ $? -ne 0 ]; then
      echo "Error: Failed to parse affected skills from feed"
      exit 1
    fi
    
    # Safely validate all installed skills before processing
    # This prevents shell injection via malicious filenames
    VALIDATED_SKILLS=()
    while IFS= read -r -d '' skill_path; do
      skill=$(basename "$skill_path")
    
      # Validate skill name BEFORE adding to array (prevents injection)
      if [[ "$skill" =~ ^[a-zA-Z0-9_-]+$ ]]; then
        VALIDATED_SKILLS+=("$skill")
      else
        echo "Warning: Skipping invalid skill name: $skill" >&2
      fi
    done < <(find "$INSTALL_DIR" -mindepth 1 -maxdepth 1 -type d -print0 2>/dev/null)
    
    # Check each validated skill against affected list
    # Use grep -qF for fixed string matching (prevents regex injection)
    for skill in "${VALIDATED_SKILLS[@]}"; do
      # At this point, $skill is guaranteed to match ^[a-zA-Z0-9_-]+$
      if echo "$AFFECTED" | grep -qF "$skill"; then
        echo "WARNING: Installed skill '$skill' has a security advisory!"
        # Get advisory details for this skill
        echo "$FEED" | jq --arg s "$skill" '.advisories[] | select(.affected[] | contains($s))'
      fi
    done

    **If you find affected skills:**

    1. Check the advisory for details and severity

    2. Notify your user immediately for critical/high severity

    3. Include the recommended action from the advisory

    ---

    Advisory Types

    | Type | Description |

    |------|-------------|

    | `malicious_skill` | Skill identified as intentionally harmful |

    | `vulnerable_skill` | Skill with security vulnerabilities |

    | `prompt_injection` | Known prompt injection pattern |

    | `attack_pattern` | Observed attack technique |

    | `best_practice` | Security recommendation |

    ---

    Severity Levels

    | Severity | Action Required |

    |----------|-----------------|

    | `critical` | Notify user immediately, take action |

    | `high` | Notify user soon, plan remediation |

    | `medium` | Notify at next interaction |

    | `low` | Log for reference |

    ---

    Prioritizing High-Exploitability Threats

    **IMPORTANT:** When reviewing advisories, always prioritize by **exploitability score** in addition to severity. The exploitability score indicates how easily a vulnerability can be exploited in practice, helping you focus on the most actionable threats.

    Exploitability Priority Levels

    | Exploitability | Meaning | Action Priority |

    |----------------|---------|-----------------|

    | `high` | Trivially or easily exploitable with public tooling | **Immediate notification** |

    | `medium` | Exploitable but requires specific conditions | **Standard notification** |

    | `low` | Difficult to exploit or theoretical | **Low priority notification** |

    How to Use Exploitability in Notifications

    1. **Filter for high-exploitability first:**

    ```bash

    # Get high exploitability advisories

    echo "$FEED" | jq '.advisories[] | select(.exploitability_score == "high")'

    ```

    2. **Include exploitability in notifications:**

    ```

    ๐Ÿ“ก ClawSec Feed: High-exploitability alert

    CRITICAL - CVE-2026-27488 (Exploitability: HIGH)

    โ†’ Trivially exploitable RCE in skill-loader v2.1.0

    โ†’ Public exploit code available

    โ†’ Recommended action: Immediate removal or upgrade to v2.1.1

    ```

    3. **Prioritize by both severity AND exploitability:**

    - A HIGH severity + HIGH exploitability CVE is more urgent than a CRITICAL severity + LOW exploitability CVE

    - Focus user attention on threats that are both severe and easily exploitable

    - Include the exploitability rationale to help users understand the risk context

    Example Notification Priority Order

    When multiple advisories exist, present them in this order:

    1. **Critical severity + High exploitability** - most urgent

    2. **High severity + High exploitability**

    3. **Critical severity + Medium/Low exploitability**

    4. **High severity + Medium/Low exploitability**

    5. **Medium/Low severity** (any exploitability)

    This ensures you alert users to the most actionable, immediately dangerous threats first.

    ---

    When to Notify Your User

    **Notify Immediately (Critical):**

  • New critical advisory affecting an installed skill
  • Active exploitation detected
  • **High exploitability score** (regardless of severity)
  • **Notify Soon (High):**

  • New high-severity advisory affecting installed skills
  • Failed to fetch advisory feed (network issue?)
  • Medium exploitability with high severity
  • **Notify at Next Interaction (Medium):**

  • New medium-severity advisories
  • General security updates
  • Low exploitability advisories
  • **Log Only (Low/Info):**

  • Low-severity advisories (mention if user asks)
  • Feed checked, no new advisories
  • Theoretical vulnerabilities (low exploitability, low severity)
  • ---

    Response Format

    If there are new advisories:

    ๐Ÿ“ก ClawSec Feed: 2 new advisories since last check
    
    CRITICAL - GA-2026-015: Malicious prompt pattern "ignore-all" (Exploitability: HIGH)
      โ†’ Detected prompt injection technique. Update your system prompt defenses.
      โ†’ Exploitability: Easily exploitable with publicly documented techniques.
    
    HIGH - GA-2026-016: Vulnerable skill "data-helper" v1.2.0 (Exploitability: MEDIUM)
      โ†’ You have this installed! Recommended action: Update to v1.2.1 or remove.
      โ†’ Exploitability: Requires specific configuration; not trivially exploitable.

    If nothing new:

    FEED_OK - Advisory feed checked, no new alerts. ๐Ÿ“ก

    ---

    State Tracking

    Track the last feed check to identify new advisories:

    {
      "schema_version": "1.0",
      "last_feed_check": "2026-02-02T15:00:00Z",
      "last_feed_updated": "2026-02-02T12:00:00Z",
      "known_advisories": ["GA-2026-001", "GA-2026-002"]
    }

    Save to: `~/.openclaw/clawsec-feed-state.json`

    State File Operations

    STATE_FILE="$HOME/.openclaw/clawsec-feed-state.json"
    
    # Create state file with secure permissions if it doesn't exist
    if [ ! -f "$STATE_FILE" ]; then
      echo '{"schema_version":"1.0","last_feed_check":null,"last_feed_updated":null,"known_advisories":[]}' > "$STATE_FILE"
      chmod 600 "$STATE_FILE"
    fi
    
    # Validate state file before reading
    if ! jq -e '.schema_version' "$STATE_FILE" >/dev/null 2>&1; then
      echo "Warning: State file corrupted or invalid schema. Creating backup and resetting."
      cp "$STATE_FILE" "${STATE_FILE}.bak.$(TZ=UTC date +%Y%m%d%H%M%S)"
      echo '{"schema_version":"1.0","last_feed_check":null,"last_feed_updated":null,"known_advisories":[]}' > "$STATE_FILE"
      chmod 600 "$STATE_FILE"
    fi
    
    # Check for major version compatibility
    SCHEMA_VER=$(jq -r '.schema_version // "0"' "$STATE_FILE")
    if [[ "${SCHEMA_VER%%.*}" != "1" ]]; then
      echo "Warning: State file schema version $SCHEMA_VER may not be compatible with this version"
    fi
    
    # Update last check time (always use UTC)
    TEMP_STATE=$(mktemp)
    if jq --arg t "$(TZ=UTC date +%Y-%m-%dT%H:%M:%SZ)" '.last_feed_check = $t' "$STATE_FILE" > "$TEMP_STATE"; then
      mv "$TEMP_STATE" "$STATE_FILE"
      chmod 600 "$STATE_FILE"
    else
      echo "Error: Failed to update state file"
      rm -f "$TEMP_STATE"
    fi

    ---

    Rate Limiting

    **Important:** To avoid excessive requests to the feed server, follow these guidelines:

    | Check Type | Recommended Interval | Minimum Interval |

    |------------|---------------------|------------------|

    | Heartbeat check | Every 15-30 minutes | 5 minutes |

    | Full feed refresh | Every 1-4 hours | 30 minutes |

    | Cross-reference scan | Once per session | 5 minutes |

    # Check if enough time has passed since last check
    STATE_FILE="$HOME/.openclaw/clawsec-feed-state.json"
    MIN_INTERVAL_SECONDS=300  # 5 minutes
    
    LAST_CHECK=$(jq -r '.last_feed_check // "1970-01-01T00:00:00Z"' "$STATE_FILE" 2>/dev/null)
    LAST_EPOCH=$(TZ=UTC date -j -f "%Y-%m-%dT%H:%M:%SZ" "$LAST_CHECK" +%s 2>/dev/null || date -d "$LAST_CHECK" +%s 2>/dev/null || echo 0)
    NOW_EPOCH=$(TZ=UTC date +%s)
    
    if [ $((NOW_EPOCH - LAST_EPOCH)) -lt $MIN_INTERVAL_SECONDS ]; then
      echo "Rate limit: Last check was less than 5 minutes ago. Skipping."
      exit 0
    fi

    ---

    Environment Variables (Optional)

    | Variable | Description | Default |

    |----------|-------------|---------|

    | `CLAWSEC_FEED_URL` | Custom advisory feed URL | Raw GitHub (`main` branch) |

    | `CLAWSEC_INSTALL_DIR` | Installation directory | `~/.openclaw/skills/clawsec-feed` |

    ---

    Updating ClawSec Feed

    Check for and install newer versions:

    # Check current installed version
    INSTALL_DIR="${CLAWSEC_INSTALL_DIR:-$HOME/.openclaw/skills/clawsec-feed}"
    CURRENT_VERSION=$(jq -r '.version' "$INSTALL_DIR/skill.json" 2>/dev/null || echo "unknown")
    echo "Installed version: $CURRENT_VERSION"
    
    # Check latest available version
    LATEST_URL="https://api.github.com/repos/prompt-security/ClawSec/releases"
    LATEST_VERSION=$(curl -sSL --fail --show-error --retry 3 --retry-delay 1 "$LATEST_URL" 2>/dev/null | \
      jq -r '[.[] | select(.tag_name | startswith("clawsec-feed-v"))][0].tag_name // empty' | \
      sed 's/clawsec-feed-v//')
    
    if [ -z "$LATEST_VERSION" ]; then
      echo "Warning: Could not determine latest version"
    else
      echo "Latest version: $LATEST_VERSION"
    
      if [ "$CURRENT_VERSION" != "$LATEST_VERSION" ]; then
        echo "Update available! Run the deployment steps with the new version."
      else
        echo "You are running the latest version."
      fi
    fi

    ---

    Initial Download Integrity

    **Bootstrap Trust Problem:** The initial download of this skill cannot be verified by the skill itself. To establish trust:

    1. **Verify the source URL** - Ensure you are downloading from `https://clawsec.prompt.security`

    2. **Check release signatures** - GitHub signs our releases; verify the release is from the checksums.

    3. **Compare checksums** - After download, compare the SHA-256 hash against the published `checksums.json`:

    # After downloading SKILL.md, verify its integrity
    EXPECTED_HASH="<hash-from-checksums.json>"
    ACTUAL_HASH=$(shasum -a 256 SKILL.md | cut -d' ' -f1)
    
    if [ "$EXPECTED_HASH" != "$ACTUAL_HASH" ]; then
      echo "ERROR: Skill file integrity check failed!"
      echo "This file may have been tampered with. Do not proceed."
      exit 1
    fi

    **Note:** For maximum security, verify checksums.json via a separate trusted channel (e.g., direct from GitHub release page UI, not via curl).

    ---

    Related Skills

  • **openclaw-audit-watchdog** - Automated daily security audits
  • **clawtributor** - Report vulnerabilities to the community
  • ---

    License

    GNU AGPL v3.0 or later - See repository for details.

    Built with ๐Ÿ“ก by the [Prompt Security](https://prompt.security) team and the agent community.

    // Comments
    Sign in with GitHub to leave a comment.
    // Related skills

    More tools from the same signal band