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 jstoup111/ai-conductor --skill exploregit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/jstoup111/ai-conductor/explore)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/explore"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/explore/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/jstoup111/ai-conductor/explore"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/explore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.02298 |
| Opus 5.5 | $0.00020 | $0.00919 |
| Sonnet 5.5 | $0.00010 | $0.00460 |
| Haiku 4.5 | $0.00005 | $0.00230 |
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 13d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
The divergent opening of DECIDE: understand intent, gather context, weigh approaches, and decide
what kind of work this is — a product feature (needs a PRD) or technical-only work
(refactor/infra/deps — no PRD). Exploration is a thinking step; its durable outputs are the chosen
approach (to .memory/decisions/) and the track marker — not a design doc.
Correctness gate: approach recommendations and the track decision are load-bearing. Apply the
/verify-claims protocol — attach a grounded confidence % to non-trivial claims about the code or
domain, surface every assumption feeding an approach, and HARD-BLOCK (operator approval interactive,
HALT if autonomous) on any unconfirmed assumption that changes which approach or track you pick.
Boundaries
explore writes no committed .docs/ design artifact. It MAY write a committed track marker
at .docs/track/<slug>.md and, for an operator-confirmed maintenance change, the matching
applicability marker at .docs/applicability/<slug>.md.
Do NOT:
- Write code, migrations, configs, tests, stubs, plans, stories, or a PRD/design doc
- Create files in
.docs/specs/,.docs/plans/,.docs/stories/, etc. - Invoke
/prd,/plan,/stories, or any other skill
Working notes (approaches considered, scratch reasoning) are ephemeral — keep them in
.pipeline/ (gitignored), never in .docs/. The PRD is authored by /prd (product track only);
stories carry acceptance criteria on both tracks.
After the track is decided and the decision persisted, exit the session immediately. The
conductor handles the handoff (to /prd on the product track, or straight to architecture on the
technical track).
Documentation-only delivery
Before selecting a normal track, determine whether the request is solely a human-facing documentation update. A request is documentation-only only when it changes no product/runtime behavior, machine-consumed contract, configuration semantics, generated artifact, or testable functional surface. If documentation accompanies any functional change, keep it on the normal product or technical route; never split it into a separate story, requirement, or plan task.
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.
- 13d ago Changed · +1 lines 869e89bd5c5b
- 22d ago Changed · +42 lines 794df78f93b1
- 2mo ago First seen · 170 lines · 50 tokens per session scan A 0fc1c87d6996
explore is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 2,298 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…