AlphaMoatによると、2026-10時点でYoder Skill Auditorのダウンロード数は7,170、スター数は3で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中3,930位、IT運用・セキュリティでは502件中116位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 7170 | 3 | - |
プラットフォームごとに集計方法と集計時点が異なります。
python3 と bash が必要です。ディレクトリ走査、導入前確認、信頼スコア、版比較、推移記録、一括分析、パイプライン向け JSON 出力を提供します。認証情報へのアクセス、プロンプト注入、ダウンロード実行などを調べます。スコアや検出結果は安全を保証しません。警告、重大な検出、入力エラーは異なる終了状態となり、重大項目への対応が必要です。理由を理解せず許可リストへ追加しません。
資料公開日 2026-10-26
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 7170 | — | 3 |
| 2026-09 | 6995 | — | 3 |
| 2026-08 | 6875 | +2.1% | 3 |
| 2026-07 | 6736 | +4.7% | 3 |
| 2026-06 | 6432 | +2.3% | 3 |
| 2026-05 | 6285 | — | 3 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
---
name: skill-auditor
version: 3.1.0
description: "The definitive security scanner for OpenClaw skills. 18 security checks including prompt injection detection, download-and-execute, privilege escalation, credential harvesting, supply chain attacks, crypto drains, and more. 5-dimension trust scoring with trend tracking."
metadata:
openclaw:
requires:
bins: ["python3", "bash"]
env: []
config: []user-invocable: true --- # Skill Auditor v3.1.0 The definitive security scanner for OpenClaw/ClawHub skills. Best-in-class detection across 18 security checks including **prompt injection detection** — the first scanner to catch agent manipulation attacks in skill documentation. 5-dimension trust scoring, trend tracking, diff analysis, and benchmarking. Zero false positives on legitimate skills. ## When to Activate 1. **Installing a new skill** from ClawHub - run `inspect.sh` for full pre-install validation 2. **Auditing existing skills** - use `audit.sh` to scan any skill directory 3. **Generating trust scores** - use `trust_score.py` for 0-100 rating across 5 dimensions 4. **Comparing skills** - use `trust_score.py --compare` for side-by-side analysis 5. **Tracking improvements** - use `trust_score.py --save-trend` to monitor score over time 6. **Reviewing updates** - use `diff-audit.sh` to compare before/after versions 7. **Batch scanning** - use `audit-all.sh` or `benchmark.sh` for fleet-wide analysis ## Quick Start ```bash # Audit a single skill bash audit.sh /path/to/skill # Trust score (0-100 across 5 dimensions) python3 trust_score.py /path/to/skill # Compare two skills side by side python3 trust_score.py /path/to/skill1 --compare /path/to/skill2 # Track score over time python3 trust_score.py /path/to/skill --save-trend python3 trust_score.py /path/to/skill --trend # Diff audit (before/after update) bash diff-audit.sh /path/to/old-version /path/to/new-version # Benchmark against a corpus bash benchmark.sh /path/to/skills-dir # Inspect a ClawHub skill before installing bash inspect.sh skill-slug # Audit all installed skills bash audit-all.sh # Generate a markdown report bash report.sh # Run test suite (28 assertions) bash test.sh ``` ## Guardrails / Anti-Patterns **DO:** - ✓ Always audit skills before installing from untrusted sources - ✓ Review trust scores - reject skills scoring below 60 (D grade) - ✓ Use `diff-audit.sh` when updating skills to catch regressions - ✓ Use `--json` output for CI/CD pipeline integration - ✓ Run `--save-trend` periodically to track skill health **DON'T:** - ✗ Install skills scoring below 40 (F grade) without extensive manual review - ✗ Ignore CRITICAL findings - they indicate potential security threats - ✗ Blindly add skills to allowlist without understanding why they access credentials - ✗ Skip audit because a skill is "popular" or "official" ## Security Checks (18 total) | # | Check | Severity | Description | |---|-------|----------|-------------| | 1 | credential-harvest | CRITICAL | Scripts reading API keys/tokens AND making network calls | | 2 | exfiltration-url | CRITICAL | webhook.site, requestbin, ngrok URLs in scripts | | 3 | obfuscated-payload | CRITICAL | Base64-encoded URLs or shell commands | | 4 | sensitive-fs | CRITICAL | /etc/passwd, ~/.ssh, ~/.aws/credentials access | | 5 | crypto-wallet | CRITICAL | Hardcoded ETH/BTC wallet addresses (drain attacks) | | 6 | dependency-confusion | CRITICAL | Internal/private-scoped packages in public deps | | 7 | typosquatting | CRITICAL | Misspelled package names (lodahs, requets, etc.) | | 8 | symlink-attack | CRITICAL | Symlinks targeting sensitive system paths | | 9 | code-execution | WARNING | eval(), exec(), subprocess patterns | | 10 | time-bomb | WARNING | Date/time comparisons that could trigger delayed payloads | | 11 | telemetry-detected | WARNING | Analytics SDKs, tracking pixels, phone-home behavior | | 12 | excessive-permissions | WARNING | >15 bins/env/config items requested | | 13 | unusual-ports | WARNING | Network calls to non-standard ports | | 14 | prompt-injection | CRITICAL | Agent manipulation in docs: "ignore instructions", role hijacking, hidden HTML directives | | 15 | download-execute | CRITICAL | curl\|bash, wget\|sh, eval $(curl), unsafe pip/npm installs | | 16 | hidden-file | WARNING | Suspicious dotfiles that may hide malicious content | | 17 | env-exfiltration | CRITICAL | Reading sensitive env vars + outbound network calls | | 18 | privilege-escalation | CRITICAL | sudo, chmod 777/setuid, writes to system paths | Context-aware: credential mentions in documentation are INFO, not CRITICAL. ## Trust Score (5 Dimensions) | Dimension | Max | What's Measured | |-----------|-----|-----------------| | Security | 35 | Audit findings (criticals = -18, warnings = -4) | | Quality | 22 | Description, version, usage docs, examples, metadata, changelog | | Structure | 18 | File organization, tests, README, reasonable scope | | Transparency | 15 | License, no minified code, code comments | | Behavioral | 10 | Rate limiting, error handling, input validation | Grades: A (90+), B (75+), C (60+), D (40+), F (<40) ### Comparative Scoring ```bash python3 trust_score.py /path/to/skill-a --compare /path/to/skill-b ``` Shows per-dimension deltas and overall score difference. ### Trend Tracking ```bash python3 trust_score.py /path/to/skill --save-trend # Record score python3 trust_score.py /path/to/skill --trend # View history ``` Stores up to 50 entries per skill in `trust_trends.json`. ## Tools | File | Purpose | |------|---------| | audit.sh | Single skill security audit (18 checks) | | audit-all.sh | Batch scan all installed skills | | trust_score.py | Trust score calculator (5-dimension, 0-100) | | diff-audit.sh | Compare skill versions for security regressions | | benchmark.sh | Corpus-wide audit with aggregate statistics | | inspect.sh | ClawHub pre-install workflow | | report.sh | Markdown report generator | | test.sh | Automated test suite (28 assertions, 12 test skills) | | allowlist.json | Known-good credential skills | ## Test Suite 12 test skills (8 malicious, 4 clean) with 28 automated assertions: ```bash bash test.sh ``` Malicious fixtures: credential harvest, obfuscated payload, sensitive fs reads, crypto wallets, time bombs, symlink attacks, prompt injection, download-execute, privilege escalation. Clean fixtures: basic skill, credential docs (false positive check), network skill, dotfiles skill. ## Exit Codes - 0: PASS / safe to install - 1: REVIEW / warnings found - 2: FAIL / critical issues - 3: Error / bad input ## Changelog See [CHANGELOG.md](CHANGELOG.md) for full version history.
钟馗.Skill——会更新漏洞库的安全审查专家。直来直去、快刀斩乱麻,三层审查(静态审计/行为模拟/供应链溯源)覆盖12类风险,输出结构化安全裁定(✅干净/⚠️可疑/🚫恶意)。Use when 用户说"审查这个Skill"、"安全检查"、"钟馗看下"、"审一下"、"查一下这个skill"、安装Skill前的安全评估、或需要审计SKILL.md的恶意载荷。
使う前にスキルパッケージの安全性を調べ、結果に応じて導入を止めるスキルです。
OpenClaw に OpenRouter の無料モデルとフォールバック連鎖を設定するツールです。
Parse, search, and analyze application logs across formats. Use when debugging from log files, setting up structured logging, analyzing error patterns, correlating events across services, parsing stack traces, or monitoring log output in real time.
Security checks for installing skills, packages, or plugins. Use BEFORE any npm install, openclaw plugins install, clawhub install, or similar install...
网络安全与SRC漏洞掘金实战技能。融合「系统学习路径」与「SRC实战掘金」双模式: ①学习模式=法律→基础→工具→靶场→攻防→就业全流程; ②实战模式=直接指导在腾讯TSRC、阿里ASRC、百度BSRC等平台挖掘高价值漏洞变现。 当用户提出以下问题时触发: "我想学网络安全怎么入门""SRC漏洞怎么挖能赚钱""渗透测试需要学什么" "Web安全漏洞原理是什么""怎么准备CTF比赛""护网面试会问什么" "云安全怎么学""挖漏洞赚钱的方法""端口扫描脚本怎么写" "SQL注入怎么检测""子域名怎么枚举""XSS漏洞怎么找" "靶场怎么搭建""Kali Linux怎么用""Metasploit怎么入门" "等保测评是什么""代码审计怎么做""内网渗透怎么学" "信息泄露漏洞怎么挖""越权漏洞怎么测试""逻辑漏洞挖掘技巧" "简历怎么写才能进安全公司""安全行业面试题有哪些" "Burp Suite怎么用""DVWA怎么安装""Pikachu靶场搭建" "Vulhub漏洞复现""网络安全法有什么规定""CTF夺旗赛怎么参加" "AWD比赛是什么""应急响应怎么做""攻击溯源怎么搞" "数据安全怎么保障""公有云安全怎么防护""私有云攻防怎么做" "云原生安全是什么"。
Unified Web penetration testing and SRC vulnerability hunting Skill. Model-driven threat modeling (12 dimensions), JSON 字段规范 state persistence, SRC/补天 compliant reporting with confirmed gate (3-layer determination). Use when user asks for authorized penetration testing, vulnerability assessment, SRC hunting (补天/Butian/vendor SRC/CNVD/众测), bug bounty, security evaluation with explicit target URL, or wants operational Recon→PoC→Report workflow. Do NOT use for CTF challenges, unauthorized testing, mobile app testing, infrastructure scanning, or social engineering.
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。