whats-next

whats-next is a skill for Claude Code from jeonnoin-alt/Eureka. It costs 63 tokens per session (3,709 once invoked), scanned A, original, MIT.

A research-project status guide for people who are stuck or unsure what to do next. It identifies the current phase of the research process and points to the specialist workflow that fits it.

In plain words
What is it for?
Diagnosing where a project stands, helping someone resume after a break, and recommending the next research skill based on the available project state.
Why use it?
It prevents researchers from repeating the wrong kind of work when the real problem is that the project has moved into a different phase.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the Eureka plugin — 16 skills, 1 agent, 1 hook shipped together

Good fit Diagnosing where a project stands, helping someone resume after a break, and recommending the next research skill based on the available project state.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeonnoin-alt/eureka/whats-next
Install

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.

Any agent
npx skills add jeonnoin-alt/Eureka --skill whats-next
Clone the repo
git clone --depth 1 https://github.com/jeonnoin-alt/Eureka

Made for: Claude Code.

Or install Eureka, the plugin that ships this one along with the rest of its 16 skills, 1 agent, 1 hook.

Wrote 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.

agentmods badge for whats-next

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/whats-next/github.svg)](https://agentmods.dev/skills/jeonnoin-alt/eureka/whats-next)
Your own site
<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/whats-next"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/whats-next/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.

agentmods 80×15 button for whats-next

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/whats-next"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/whats-next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,709 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.03709
Opus 5 $0.00032 $0.01854
Sonnet 5 $0.00013 $0.00742
Haiku 4.5 $0.00006 $0.00371

Measured 12d ago against content hash 3af5835f0fc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

whats-next 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 12d 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.

skills/whats-next/SKILL.md · 250 lines

How it starts

The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What's Next?

Overview

Researchers get stuck. Not because they're lazy or incompetent — because the research lifecycle has many branches, every project has different state, and "what should I do now?" is a hard question even for experienced PIs.

This skill diagnoses where you are in the research lifecycle, then recommends the next Eureka skill to invoke. It does NOT do the work itself. It is a router — it figures out which specialist to call.

Core principle: When stuck, the answer is almost never "try harder at what you're doing." The answer is usually "you're in a different phase than you think — switch tools."

Modes

This skill has two modes:

Diagnostic mode (default)

User doesn't know where they are in the research lifecycle, or needs help picking the next skill. Scan state → diagnose phase → recommend specialist skill. This is the existing workflow (Steps 1-6 below).

Resume mode (NEW in v1.10.0)

User returns after a break and wants to continue where they left off. Trigger phrases: "resume", "continue", "last session", "where was I", "어디서부터", "이어서".

Resume workflow:

  1. Read the most recent entry in docs/eureka/journal/ (sort by filename YYYY-MM-DD.md). If no journal entry exists, fall back to Diagnostic mode.
  2. Read the last 20 commits of git log --oneline -20 for context on what was worked on.
  3. Scan docs/eureka/ subdirectories for most-recently-modified artifacts:
    • designs/ — any new design docs?
    • registrations/ — any new or amended registrations? (check INDEX.md)
    • plans/ — any experiment plans in progress?
    • audits/ — recent claims-audit runs?
    • reviews/ — recent research-reviewer runs?
    • novelty-audits/ — recent novelty audits?
    • verifications/ — recent verification runs?
  4. Synthesize: "Last session ended at [phase] based on [evidence]. Expected next step is [skill]. Context in 3 sentences: [...]. Proceed with [skill]?"
  5. Wait for user confirmation, then hand off to the recommended skill.

Read the full file on GitHub · 250 lines

Changes

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.

  1. 12d ago First seen · 250 lines · 63 tokens per session scan A 3af5835f0fc2

Subscribe to this mod's changes

whats-next is a skill published in the GitHub repository jeonnoin-alt/Eureka (2 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 3,709 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-31.

Related

Other skills, from other repositories

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…

cbrock84/headcount · 93 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens