Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/blessonism/openclaw-skillsnpx agentmods add skills/blessonism/openclaw-skills/github-explorerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/blessonism/openclaw-skills/github-explorer)<a href="https://agentmods.dev/skills/blessonism/openclaw-skills/github-explorer"><img src="https://agentmods.dev/badge/skills/blessonism/openclaw-skills/github-explorer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/blessonism/openclaw-skills/github-explorer"><img src="https://agentmods.dev/badge/skills/blessonism/openclaw-skills/github-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00083 | $0.03086 |
| Opus 5.5 | $0.00033 | $0.01234 |
| Sonnet 5.5 | $0.00017 | $0.00617 |
| Haiku 4.5 | $0.00008 | $0.00309 |
Grade A, and why
github-explorer scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- README: `curl -s -H "Authorization: token {PAT}" -H "Accept: application/vnd.github.v3.raw" "https://api.github.com/repos/{owner}/{repo}/readme"` This is a copy
100% identical to github-explorer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Explorer — 项目深度分析
Philosophy: README 只是门面,真正的价值藏在 Issues、Commits 和社区讨论里。
Workflow
[项目名] → [1. 定位 Repo] → [2. 多源采集] → [3. 分析研判] → [4. 结构化输出]
Phase 1: 定位 Repo
- 用
web_search搜索site:github.com <project_name>确认完整 org/repo - 用
search-layer(Deep 模式 + 意图感知)补充获取社区链接和非 GitHub 资源:python3 skills/search-layer/scripts/search.py \ --queries "<project_name> review" "<project_name> 评测 使用体验" \ --mode deep --intent exploratory --num 5 - 用
web_fetch抓取 repo 主页获取基础信息(README、Stars、Forks、License、最近更新)
Phase 2: 多源采集(并行)
⚠️ GitHub 页面抓取规则(强制):GitHub repo 页面是 SPA(客户端渲染),web_fetch 只能拿到导航栏壳子,禁止用 web_fetch 抓 github.com 的 repo 页面。一律使用 GitHub API:
- README:
curl -s -H "Authorization: token {PAT}" -H "Accept: application/vnd.github.v3.raw" "https://api.github.com/repos/{owner}/{repo}/readme" - Repo 元数据:
curl -s -H "Authorization: token {PAT}" "https://api.github.com/repos/{owner}/{repo}" - Issues:
curl -s -H "Authorization: token {PAT}" "https://api.github.com/repos/{owner}/{repo}/issues?state=all&sort=comments&per_page=10" - Commits:
curl -s -H "Authorization: token {PAT}" "https://api.github.com/repos/{owner}/{repo}/commits?per_page=10" - File tree:
curl -s -H "Authorization: token {PAT}" "https://api.github.com/repos/{owner}/{repo}/git/trees/{branch}?recursive=1"
PAT 见 TOOLS.md。
以下来源按需检查,有则采集,无则跳过:
| 来源 | URL 模式 | 采集内容 | 建议工具 |
|---|---|---|---|
| GitHub Repo | github.com/{org}/{repo} |
README、About、Contributors | web_fetch |
| GitHub Issues | github.com/{org}/{repo}/issues?q=sort:comments |
Top 3-5 高质量 Issue | browser |
| 中文社区 | 微信/知乎/小红书 | 深度评测、使用经验 | content-extract |
| 技术博客 | Medium/Dev.to | 技术架构分析 | web_fetch / content-extract |
| 讨论区 | V2EX/Reddit | 用户反馈、槽点 | search-layer(Deep 模式) |
search-layer 调用规范
search-layer v2 支持意图感知评分。github-explorer 场景下的推荐用法:
| 场景 | 命令 | 说明 |
|---|---|---|
| 项目调研(默认) | python3 skills/search-layer/scripts/search.py --queries "<project> review" "<project> 评测" --mode deep --intent exploratory --num 5 |
多查询并行,按权威性排序 |
| 最新动态 | python3 skills/search-layer/scripts/search.py "<project> latest release" --mode deep --intent status --freshness pw --num 5 |
优先新鲜度,过滤一周内 |
| 竞品对比 | python3 skills/search-layer/scripts/search.py --queries "<project> vs <competitor>" "<project> alternatives" --mode deep --intent comparison --num 5 |
对比意图,关键词+权威双权重 |
| 快速查链接 | python3 skills/search-layer/scripts/search.py "<project> official docs" --mode fast --intent resource --num 3 |
精确匹配,最快 |
| 社区讨论 | python3 skills/search-layer/scripts/search.py "<project> discussion experience" --mode deep --intent exploratory --domain-boost reddit.com,news.ycombinator.com --num 5 |
加权社区站点 |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 221 lines · 83 tokens per session scan A 8092c32d94a0
github-explorer is a skill published in the GitHub repository blessonism/openclaw-skills (55 stars, last pushed 7mo ago), licensed MIT. It adds 83 tokens to every session and 3,086 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to github-explorer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github
Manage GitHub issues and pull requests, inspect CI runs, and query repository data.
update-nanoclaw
Transactionally update a customized NanoClaw checkout from official upstream without exposing live mounted source, with fork-safe skill refresh, mutable-state snapshots, migration gates, exact-code upgrade markers, detected service restart, health verification, and automatic local rollback. Use for routine merge…
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
git-delegation
A procedure for sending Git version-control commands to a separate Manager instead of running them directly. Git is the tool used to track code changes and work with repositories.
github-operations
A tool for managing GitHub pull requests and issues. Pull requests are proposed code changes for review, while issues are GitHub's way to track bugs, tasks, and questions.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…