sos

<!-- SVK Version Check — runs once per session on first skill invocation --> <svk-version-check> **On first invocation this session**, silently perform a version check: 1. Look for `.claude/svk-meta.json` in the current project. If it doesn't exist, skip this check entirely. 2. Read the `svk_repo` path and `installed_version` from the metadata file. 3. Run: `git -C <svk_repo> fetch --tags --quiet 2>/dev/null` 4. Run: `git -C <svk_repo> tag --sort=-v:refname | head -1` to get the latest tag. 5. Compare the installed version against the latest tag (strip the leading `v`). 6. If they match, skip — the user is up to date. 7. If the latest tag is newer, show this message ONCE (never repeat in this session): > **SVK Update Available:** v{latest} is available (you're on v{installed}). > - **Update now:** I can pull and reinstall the changed skills in this session > - **Update later:** Start a new chat and run `/SVK:update` 8. If the git commands fail (offline, repo moved, etc.), skip silently. Never show errors from version checking. **Important:** Do NOT block or delay the user's actual command. Perform this check, show the notification if needed, then proceed with the command they invoked. </svk-version-check> # Stronghold of Security A comprehensive, multi-agent adversarial security audit pipeline for Solana/Anchor smart contracts. > *"The best defense is a thorough offense."* --- ## Getting Started Stronghold of Security runs as a multi-phase pipeline. Each phase is a ...