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/kirkchen/beat/explorenpx skills add kirkchen/beat --skill exploregit clone --depth 1 https://github.com/kirkchen/beatWhat 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.00023 | $0.01437 |
| Opus 5 | $0.00012 | $0.00718 |
| Sonnet 5 | $0.00005 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00144 |
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 2d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
<decision_boundary>
Use for:
- Thinking through ideas, requirements, or problems before committing to a change
- Investigating the codebase to understand architecture, feasibility, or hidden complexity
- Comparing approaches and surfacing risks without producing code
NOT for:
- Creating spec artifacts as a structured workflow (use
/beat:design) - Breaking down tasks (use
/beat:plan) - Implementing code (use
/beat:apply) - Extracting specs from existing code (use
/beat:distill)
Trigger examples:
- "Let me think through X" / "Investigate why Y happens" / "What are our options for Z?"
- Should NOT trigger: "design a feature" / "implement this" / "break down the tasks"
</decision_boundary>
IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first (e.g., /beat:design). You MAY create Beat artifacts (proposals, designs, features) if the user asks -- that's capturing thinking, not implementing.
This is a stance, not a workflow. No fixed steps, no required sequence, no mandatory outputs. You're a thinking partner.
Prerequisites (invoke before proceeding)
| Superpower | When | Priority |
|---|---|---|
| brainstorming | At the start of explore, before any response | MUST |
If unavailable (skill not installed), proceed directly into the thinking stance.
Rationalization Prevention
| Thought | Reality |
|---|---|
| "The user wants a quick answer, brainstorming will slow us down" | Brainstorming IS the answer — it surfaces assumptions and alternatives. Quick answers skip the thinking explore is meant to provide. |
| "This topic is too simple for brainstorming" | Simple topics finish brainstorming quickly. The overhead is negligible, but the missed insight is not. |
| "I already understand what the user wants" | Understanding the question ≠ exploring the problem space. Brainstorming prevents premature convergence. |
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.
- 2d ago First seen · 156 lines · 23 tokens per session scan A 8b4dddf03b20
explore is a skill published in the GitHub repository kirkchen/beat (7 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,437 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-08-31.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…