[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734ZXW7PJWT9QMS48BH23H7":3,"skill-same:01M734ZXW7PJWT9QMS48BH23H7":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M734ZXW7PJWT9QMS48BH23H7","leak-check",null,"Scan codebase and git history for leaked secrets — API keys, tokens, passwords, private keys. Uses whispers-style regex patterns + gitleaks. Run as \u002Fleak-check before any git push. Alerts on Claude API keys, GitHub tokens, AWS credentials, and generic high-entropy strings.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fleak-check\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: leak-check\ndescription: Scan codebase and git history for leaked secrets — API keys, tokens, passwords, private keys. Uses whispers-style regex patterns + gitleaks. Run as \u002Fleak-check before any git push. Alerts on Claude API keys, GitHub tokens, AWS credentials, and generic high-entropy strings.\norigin: Skyscanner\u002Fwhispers + gitleaks\u002Fgitleaks (MIT) + marionevra\u002Fawesome-ai-agents-security patterns\nlicense: MIT\nversion: 1.0.0\ncompatibility: bash, git, any project type\n---\n\n# leak-check\n\n## When to Use\n\n- Before every `git push` (add to pre-push hook)\n- After adding new config files, .env samples, or API integration code\n- When onboarding a new developer — scan the full history\n- Whenever the CI pipeline flags a suspicious commit\n- Triggered by: `\u002Fleak-check`, \"scan for leaked secrets\", \"check for exposed tokens\", \"are there any API keys in the repo\"\n\n## Do NOT use for\n\n- Runtime secret rotation (use vault\u002FSSM for that)\n- Encrypting secrets — this is detection only, not remediation\n- Replacing a proper secrets manager (see `supply-chain-security` skill for full supply-chain hardening)\n\n---\n\n## Quick Scan (regex-based, no install required)\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\n# Fast in-repo scan without external tools\n\nPATTERNS=(\n  # Anthropic \u002F Claude\n  \"sk-ant-[a-zA-Z0-9_-]{20,}\"\n  # OpenAI\n  \"sk-[a-zA-Z0-9]{48}\"\n  # GitHub tokens\n  \"gh[pos]_[A-Za-z0-9_]{36}\"\n  \"github_pat_[A-Za-z0-9_]{82}\"\n  # AWS\n  \"AKIA[0-9A-Z]{16}\"\n  \"aws_secret_access_key\\s*=\\s*[A-Za-z0-9\u002F+=]{40}\"\n  # Generic private key\n  \"-----BEGIN (RSA |EC |OPENSSH )?PRIVATE KEY-----\"\n  # Generic high-entropy assignment\n  \"(api_key|apikey|secret|password|token|passwd)\\s*[=:]\\s*['\\\"][A-Za-z0-9+\u002F=_-]{20,}['\\\"]\"\n)\n\nFOUND=0\nfor pattern in \"${PATTERNS[@]}\"; do\n  matches=$(git grep -rniE \"$pattern\" -- ':!*.lock' ':!node_modules' ':!vendor' 2>\u002Fdev\u002Fnull || true)\n  if [[ -n \"$matches\" ]]; then\n    echo \"LEAK DETECTED — pattern: $pattern\"\n    echo \"$matches\"\n    FOUND=$((FOUND+1))\n  fi\ndone\n\n# Also scan git log for secrets in commit messages\ngit log --all --oneline | grep -iE \"(api.?key|secret|password|token)\" | head -5 && \\\n  echo \"WARNING: suspicious words found in commit messages — review above\"\n\n[[ $FOUND -eq 0 ]] && echo \"CLEAN — no secrets detected\" || exit 1\n```\n\n---\n\n## Full Scan with gitleaks\n\n```bash\n# Install (one-time)\nbrew install gitleaks          # macOS\n# or: docker run --rm -v $(pwd):\u002Fpath zricethezav\u002Fgitleaks\n\n# Scan working directory\ngitleaks detect --source . --verbose\n\n# Scan entire git history\ngitleaks detect --source . --log-opts=\"--all\" --verbose\n\n# Generate SARIF report for GitHub\ngitleaks detect --source . --report-format sarif --report-path gitleaks-report.sarif\n```\n\n---\n\n## Pre-Push Hook Integration\n\n```bash\n# .git\u002Fhooks\u002Fpre-push (make executable: chmod +x .git\u002Fhooks\u002Fpre-push)\n#!\u002Fusr\u002Fbin\u002Fenv bash\necho \"[yamtam\u002Fleak-check] Scanning for secrets before push...\"\n\n# Quick regex scan\nFOUND=0\nfor pattern in \\\n  \"sk-ant-[a-zA-Z0-9_-]{20,}\" \\\n  \"AKIA[0-9A-Z]{16}\" \\\n  \"gh[pos]_[A-Za-z0-9_]{36}\" \\\n  \"-----BEGIN.*PRIVATE KEY-----\"; do\n  if git grep -rqiE \"$pattern\" -- ':!*.lock' ':!node_modules' 2>\u002Fdev\u002Fnull; then\n    echo \"BLOCKED: secret pattern detected ($pattern)\"\n    FOUND=$((FOUND+1))\n  fi\ndone\n\n[[ $FOUND -gt 0 ]] && exit 1\necho \"[leak-check] CLEAN — push allowed\"\nexit 0\n```\n\n---\n\n## Remediation Steps (If Leak Found)\n\n```bash\n# 1. Invalidate the leaked credential IMMEDIATELY (before anything else)\n#    Claude API: anthropic.com\u002Fconsole → API Keys → Revoke\n#    GitHub: Settings → Developer settings → Personal access tokens → Delete\n\n# 2. Remove from working tree\necho \"SECRET_KEY=\" > .env   # replace with placeholder\n\n# 3. Rewrite git history (use BFG for large repos)\n# Option A — BFG (recommended for large histories)\njava -jar bfg.jar --replace-text patterns.txt .git\n\n# Option B — git filter-repo\ngit filter-repo --path-glob '**\u002F.env' --invert-paths\n\n# 4. Force push (requires human authorization — see git-push-enforcement.md)\ngit push --force-with-lease\n\n# 5. Log the incident\nbash core\u002Fscripts\u002Fsecure-logger.sh \"incident\" \"secret leaked: \u003Ctype>, revoked, history rewritten at $(git rev-parse HEAD)\"\n```\n\n---\n\n## CI Integration (GitHub Actions)\n\n```yaml\n# .github\u002Fworkflows\u002Fsecret-scan.yml\nname: Secret Scan\non: [push, pull_request]\njobs:\n  gitleaks:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with: { fetch-depth: 0 }\n      - uses: gitleaks\u002Fgitleaks-action@v2\n        env:\n          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n- [ ] Scan ran against full git history (`--all`), not just working directory\n- [ ] Anthropic\u002FClaude API key pattern `sk-ant-*` explicitly in scan patterns\n- [ ] Pre-push hook installed and executable (verify: `ls -la .git\u002Fhooks\u002Fpre-push`)\n- [ ] `.env` files in `.gitignore` — confirm with `git check-ignore -v .env`\n- [ ] Any detected secrets invalidated in the provider console BEFORE history rewrite\n- [ ] Incident logged to `core\u002Fmemory\u002Faudit\u002Fagent-actions.log` via secure-logger.sh\n- [ ] CI gitleaks action runs on every PR (no merge without CLEAN status)\n","# leak-check\n\n## When to Use\n\n- Before every `git push` (add to pre-push hook)\n- After adding new config files, .env samples, or API integration code\n- When onboarding a new developer — scan the full history\n- Whenever the CI pipeline flags a suspicious commit\n- Triggered by: `\u002Fleak-check`, \"scan for leaked secrets\", \"check for exposed tokens\", \"are there any API keys in the repo\"\n\n## Do NOT use for\n\n- Runtime secret rotation (use vault\u002FSSM for that)\n- Encrypting secrets — this is detection only, not remediation\n- Replacing a proper secrets manager (see `supply-chain-security` skill for full supply-chain hardening)\n\n---\n\n## Quick Scan (regex-based, no install required)\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\n# Fast in-repo scan without external tools\n\nPATTERNS=(\n  # Anthropic \u002F Claude\n  \"sk-ant-[a-zA-Z0-9_-]{20,}\"\n  # OpenAI\n  \"sk-[a-zA-Z0-9]{48}\"\n  # GitHub tokens\n  \"gh[pos]_[A-Za-z0-9_]{36}\"\n  \"github_pat_[A-Za-z0-9_]{82}\"\n  # AWS\n  \"AKIA[0-9A-Z]{16}\"\n  \"aws_secret_access_key\\s*=\\s*[A-Za-z0-9\u002F+=]{40}\"\n  # Generic private key\n  \"-----BEGIN (RSA |EC |OPENSSH )?PRIVATE KEY-----\"\n  # Generic high-entropy assignment\n  \"(api_key|apikey|secret|password|token|passwd)\\s*[=:]\\s*['\\\"][A-Za-z0-9+\u002F=_-]{20,}['\\\"]\"\n)\n\nFOUND=0\nfor pattern in \"${PATTERNS[@]}\"; do\n  matches=$(git grep -rniE \"$pattern\" -- ':!*.lock' ':!node_modules' ':!vendor' 2>\u002Fdev\u002Fnull || true)\n  if [[ -n \"$matches\" ]]; then\n    echo \"LEAK DETECTED — pattern: $pattern\"\n    echo \"$matches\"\n    FOUND=$((FOUND+1))\n  fi\ndone\n\n# Also scan git log for secrets in commit messages\ngit log --all --oneline | grep -iE \"(api.?key|secret|password|token)\" | head -5 && \\\n  echo \"WARNING: suspicious words found in commit messages — review above\"\n\n[[ $FOUND -eq 0 ]] && echo \"CLEAN — no secrets detected\" || exit 1\n```\n\n---\n\n## Full Scan with gitleaks\n\n```bash\n# Install (one-time)\nbrew install gitleaks          # macOS\n# or: docker run --rm -v $(pwd):\u002Fpath zricethezav\u002Fgitleaks\n\n# Scan working directory\ngitleaks detect --source . --verbose\n\n# Scan entire git history\ngitleaks detect --source . --log-opts=\"--all\" --verbose\n\n# Generate SARIF report for GitHub\ngitleaks detect --source . --report-format sarif --report-path gitleaks-report.sarif\n```\n\n---\n\n## Pre-Push Hook Integration\n\n```bash\n# .git\u002Fhooks\u002Fpre-push (make executable: chmod +x .git\u002Fhooks\u002Fpre-push)\n#!\u002Fusr\u002Fbin\u002Fenv bash\necho \"[yamtam\u002Fleak-check] Scanning for secrets before push...\"\n\n# Quick regex scan\nFOUND=0\nfor pattern in \\\n  \"sk-ant-[a-zA-Z0-9_-]{20,}\" \\\n  \"AKIA[0-9A-Z]{16}\" \\\n  \"gh[pos]_[A-Za-z0-9_]{36}\" \\\n  \"-----BEGIN.*PRIVATE KEY-----\"; do\n  if git grep -rqiE \"$pattern\" -- ':!*.lock' ':!node_modules' 2>\u002Fdev\u002Fnull; then\n    echo \"BLOCKED: secret pattern detected ($pattern)\"\n    FOUND=$((FOUND+1))\n  fi\ndone\n\n[[ $FOUND -gt 0 ]] && exit 1\necho \"[leak-check] CLEAN — push allowed\"\nexit 0\n```\n\n---\n\n## Remediation Steps (If Leak Found)\n\n```bash\n# 1. Invalidate the leaked credential IMMEDIATELY (before anything else)\n#    Claude API: anthropic.com\u002Fconsole → API Keys → Revoke\n#    GitHub: Settings → Developer settings → Personal access tokens → Delete\n\n# 2. Remove from working tree\necho \"SECRET_KEY=\" > .env   # replace with placeholder\n\n# 3. Rewrite git history (use BFG for large repos)\n# Option A — BFG (recommended for large histories)\njava -jar bfg.jar --replace-text patterns.txt .git\n\n# Option B — git filter-repo\ngit filter-repo --path-glob '**\u002F.env' --invert-paths\n\n# 4. Force push (requires human authorization — see git-push-enforcement.md)\ngit push --force-with-lease\n\n# 5. Log the incident\nbash core\u002Fscripts\u002Fsecure-logger.sh \"incident\" \"secret leaked: \u003Ctype>, revoked, history rewritten at $(git rev-parse HEAD)\"\n```\n\n---\n\n## CI Integration (GitHub Actions)\n\n```yaml\n# .github\u002Fworkflows\u002Fsecret-scan.yml\nname: Secret Scan\non: [push, pull_request]\njobs:\n  gitleaks:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with: { fetch-depth: 0 }\n      - uses: gitleaks\u002Fgitleaks-action@v2\n        env:\n          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n- [ ] Scan ran against full git history (`--all`), not just working directory\n- [ ] Anthropic\u002FClaude API key pattern `sk-ant-*` explicitly in scan patterns\n- [ ] Pre-push hook installed and executable (verify: `ls -la .git\u002Fhooks\u002Fpre-push`)\n- [ ] `.env` files in `.gitignore` — confirm with `git check-ignore -v .env`\n- [ ] Any detected secrets invalidated in the provider console BEFORE history rewrite\n- [ ] Incident logged to `core\u002Fmemory\u002Faudit\u002Fagent-actions.log` via secure-logger.sh\n- [ ] CI gitleaks action runs on every PR (no merge without CLEAN status)\n",{"name":5,"origin":24,"license":15,"version":25,"description":7,"compatibility":26},"Skyscanner\u002Fwhispers + gitleaks\u002Fgitleaks (MIT) + marionevra\u002Fawesome-ai-agents-security patterns","1.0.0","bash, git, any project type","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fleak-check",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill leak-check",{"tool":43,"command":44},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill leak-check",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill leak-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fleak-check\u002FSKILL.md",true,[],[52,59,67,75,83,91],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]