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 agentmods add skills/yonatangross/orchestkit/explorenpx skills add yonatangross/orchestkit --skill exploregit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/explore)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/explore"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/explore.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 | $0.00068 | $0.03979 |
| Opus 5 | $0.00034 | $0.01989 |
| Sonnet 5 | $0.00014 | $0.00796 |
| Haiku 4.5 | $0.00007 | $0.00398 |
Grade A, and why
explore 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 today.
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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Exploration
Multi-angle codebase exploration using 3-5 parallel agents.
🎯 Quick Start
/ork:explore authentication
Opus 5: Exploration agents use native adaptive thinking for deeper pattern recognition across large codebases.
STEP -0.5: Effort-Aware Agent Scaling (CC 2.1.120+)
Read $CLAUDE_EFFORT to scale exploration depth before any other decision.
# CC 2.1.120+ env var; explicit --effort= overrides
EFFORT = os.environ.get("CLAUDE_EFFORT")
for token in "$ARGUMENTS".split():
if token.startswith("--effort="):
EFFORT = token.split("=", 1)[1]
EFFORT = EFFORT or "high" # default
| Effort | Agent count | Phases | Time |
|---|---|---|---|
low |
1 (structure-only) | 1, 2, 8 | ~1 min |
medium |
2 (structure + data flow) | 1, 2, 3 (subset), 8 | ~3 min |
high (default) |
4 (full parallel team) | 1–8 | ~6 min |
xhigh (Opus 5) |
5 (+ uncertainty pass on health scores) | 1–8 + caveats | ~8 min |
Override gate: if the user passes --effort=high explicitly while $CLAUDE_EFFORT is low, the flag wins. /ork:doctor warns when xhigh is requested without Opus 5.
STEP 0: Verify User Intent with AskUserQuestion
BEFORE creating tasks, clarify what the user wants to explore:
AskUserQuestion(
questions=[{
"question": "What aspect do you want to explore?",
"header": "Focus",
"options": [
{"label": "Full exploration (Recommended)", "description": "Code structure + data flow + architecture + health assessment"},
{"label": "Quick scan", "description": "Find relevant files + structure, skip deep analysis"},
{"label": "Data flow", "description": "Trace how data moves through the system"},
{"label": "Architecture patterns", "description": "Identify design patterns and integrations"}
],
"multiSelect": false
}]
)
Based on answer, adjust workflow:
- Full exploration: All phases, all parallel agents
- Quick scan: Files + structure only (phases 1-2), skip health/deps/product — no deep agents
- Data flow: Focus phase 3 agents on data tracing
- Architecture patterns: Focus on backend-system-architect agent
What ships with it
18 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.
- assets/exploration-report.md 1.3 KB
- assets/hotspot-diagram.md 2.9 KB
- references/code-health-rubric.md 2.5 KB
- references/dashboard-example.json 2.3 KB
- references/dashboard-spec.md 5.6 KB
- references/dependency-analysis.md 2.0 KB
- references/exploration-report-template.md 1.4 KB
- references/findability-patterns.md 2.4 KB
- rules/_sections.md 710 B
- rules/agent-teams-mode.md 3.4 KB
- rules/code-health-assessment.md 2.2 KB
- rules/dependency-hotspot-analysis.md 2.1 KB
- rules/exploration-agents.md 3.4 KB
- rules/product-perspective.md 2.4 KB
- scripts/dependency-mapper.sh 3.7 KB runs code
- scripts/post_explore_summary.py 8.0 KB runs code
- scripts/render-spec.mjs 7.3 KB runs code
- test-cases.json 4.7 KB
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.
- today First seen · 348 lines · 68 tokens per session scan A 27e2a159db10
explore is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 3,979 once invoked, about $0.0003 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
context-builder
Gather comprehensive project context before starting implementation. Use at the beginning of complex tasks to understand codebase structure, dependencies, patterns, and conventions before writing code.
repo-onboarding
Systematically map an unfamiliar codebase before changing it — entry points, build/test loop, conventions, data flow. Use when starting work in a repo you haven't seen, or asked "how does this codebase work?".
repository-discovery
Use this skill to systematically explore an unfamiliar codebase before making any changes. Activates when starting work in an unknown repository, adding a new feature, debugging without prior context, or when no CONTEXT.md exists. Produces a grounded understanding of architecture, conventions, and constraints.
codebase-onboarding
Use when you land in an unfamiliar or inherited codebase and must get productive fast: a breadth-first map of entry points, request flow, module ownership, hidden side effects (cron, webhooks, workers) and churn hotspots, committed as CODEBASE-MAP.md. NOT a deep audit of one module (that is analyze) or chasing one…
convert-three-locks
Architect the Three Locks persuasion sequence: Lock 1 Want (sell the state), Lock 2 Trust (earn belief through proof + voice), Lock 3 Excuse (give the rational justification). Outputs the lock-by-lock blueprint that the rest of the asset writes against. Use when planning the persuasion architecture of a sales page…
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.