Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add xiaobei930/cc-best --skill explorationgit clone --depth 1 https://github.com/xiaobei930/cc-bestWrote 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/xiaobei930/cc-best/exploration)<a href="https://agentmods.dev/skills/xiaobei930/cc-best/exploration"><img src="https://agentmods.dev/badge/skills/xiaobei930/cc-best/exploration.svg" alt="Measured on agentmods" 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.00024 | $0.01070 |
| Opus 5 | $0.00012 | $0.00535 |
| Sonnet 5 | $0.00005 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
exploration scanned grade A with 0 findings 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 4d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
代码库探索
本技能提供代码库探索的通用方法论，包含两种策略模式。
子文件
- isolated-research.md - 隔离研究（快速一次性探索）
- iterative-retrieval.md - 渐进式检索（多轮迭代探索）
策略选择
| 场景 | 推荐策略 | 原因 |
|---|---|---|
| 快速了解某个模块 | isolated-research | 一次性探索，不污染上下文 |
| 理解复杂的跨模块流程 | iterative-retrieval | 需要多轮精炼 |
| 简单的文件/函数定位 | 直接 Grep/Glob | 无需完整探索流程 |
| 新项目初始理解 | iterative-retrieval | 需要建立全局认知 |
| 调试特定 Bug | isolated-research | 聚焦单一问题 |
| 架构分析和文档化 | iterative-retrieval | 需要完整依赖图 |
通用探索方法
搜索工具选择
| 目标 | 工具 | 示例 |
|---|---|---|
| 按文件名/路径查找 | Glob | **/auth/**/*.ts |
| 按代码内容查找 | Grep | "function authenticate" |
| 读取完整文件 | Read | 直接读取已知路径文件 |
| 深度子任务（隔离） | Task | 派发子代理执行 |
搜索策略模式
## 入口点搜索
- 路由/API 端点
- 中间件
- main/index 文件
- 配置文件
## 定义搜索
- class/function 定义
- type/interface 定义
- 常量/枚举定义
## 使用搜索
- import/require 语句
- 函数调用点
- 类实例化
## 依赖搜索
- package.json
- import 图谱
- 模块边界
输出格式（通用）
所有探索结果应遵循统一格式：
## 探索报告
### 问题/目标
[描述探索的目标]
### 关键发现
| 文件 | 行号 | 功能说明 |
| ------------------- | ---- | -------------- |
| `src/auth/login.ts` | 42 | 登录验证入口 |
| `src/lib/jwt.ts` | 15 | Token 生成逻辑 |
### 依赖关系
[可选：模块依赖图、调用链]
### 结论
[对问题的回答]
### 后续建议
[可选：建议的下一步动作]
子策略
1. isolated-research（隔离研究）
特点：
- 在子代理中执行，不污染主上下文
- 一次性任务，快速返回
- 适合聚焦的单一问题
详细指南参阅 isolated-research.md
2. iterative-retrieval（迭代检索）
特点：
- 多轮迭代，逐步精炼
- 置信度评估驱动
- 适合复杂跨模块问题
详细指南参阅 iterative-retrieval.md
与角色系统配合
| 角色 | 探索场景 | 推荐策略 |
|---|---|---|
/cc-best:pm |
理解现有功能 | isolated-research |
/cc-best:lead |
架构分析、技术设计 | iterative-retrieval |
/cc-best:dev |
实现前了解相关代码 | isolated-research |
/cc-best:qa |
理解测试范围 | isolated-research |
/cc-best:fix |
追踪 Bug 根因 | iterative-retrieval |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 153 lines · 24 tokens per session scan A cda25b84c748
exploration is a skill published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 1,070 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…