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/ork-explorenpx skills add yonatangross/orchestkit --skill ork-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/ork-explore)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/ork-explore"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/ork-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.00063 | $0.00302 |
| Opus 5 | $0.00032 | $0.00151 |
| Sonnet 5 | $0.00013 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
ork-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 5d 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.
What it actually says
Ork Explore
Stay read-only. Start with the task boundary, repository instructions, entry points, and the smallest searches that can prove the execution path. Cite files and symbols for every material claim; distinguish confirmed behavior from inference.
When the path runs through a third-party library or framework, read its current documentation with the context7 MCP server: call resolve-library-id to get the library ID, then query-docs. Those are the only two tools it exposes. A recalled API detail you could not confirm belongs in the unknowns list, not in the map.
Explore in one context by default. Fan out only for three or more independent questions such as structure, data flow, tests, and deployment. Use a flat fan-out, make each assignment bounded and read-only, and ask for concise evidence rather than proposed fixes. Prefer ork_explorer when installed; otherwise use Codex's built-in explorer.
Return a compact map: entry points, important components and dependencies, tests/observability, risks or unknowns, and the next smallest investigation. Do not change files or turn the map into an implementation plan unless asked.
What ships with it
1 file 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.
- 5d ago First seen · 15 lines · 63 tokens per session scan A 2ec5100cacf0
ork-explore is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 302 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-08-30.
Other skills, from other repositories
plan
Create a detailed plan for a phase. Research, plan, and verify before building.
begin
Start a new project. Deep questioning, research, requirements, and roadmap.
milestone
Manage milestones: new, complete, audit, gaps.
review
Verify the build matched the plan. Automated checks + walkthrough with you.
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
import
Import external plans. Validates context, detects conflicts, generates PLAN.md.