Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add primeline-ai/evolving-lite/plugin install evolving-liteWrote 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/commands/primeline-ai/evolving-lite/whats-next)<a href="https://agentmods.dev/commands/primeline-ai/evolving-lite/whats-next"><img src="https://agentmods.dev/badge/commands/primeline-ai/evolving-lite/whats-next.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.1 | $0.00008 | $0.00312 |
| Opus 5 | $0.00004 | $0.00156 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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 6d 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
Show where we are and what to do next.
Process
-
Read project state:
${CLAUDE_PLUGIN_ROOT}/_memory/index.jsonfor active project${CLAUDE_PLUGIN_ROOT}/_memory/projects/{project}.jsonfor progress- Most recent file in
${CLAUDE_PLUGIN_ROOT}/_memory/sessions/for last session summary
-
Show status:
Project: {name or "No active project"}
Last session: {date} - {summary}
Progress: {last 3 entries}
Next step: {suggested next action}
-
If no active project: List available project files in
_memory/projects/or suggest creating one. -
If resuming after a break: Check for handoff documents in
_memory/sessions/and present the most recent one.
Creating a Handoff
If the user is ending a session, create a handoff:
# Session Handoff - {date}
## What was done
- {action 1}
- {action 2}
## Current state
- {what's working}
- {what's broken/incomplete}
## Next steps
1. {most important next action}
2. {second priority}
## Open questions
- {anything unresolved}
Save to ${CLAUDE_PLUGIN_ROOT}/_memory/sessions/handoff-{date}.md
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.
- 6d ago First seen · 51 lines · 8 tokens per session scan A fe7d8d9d61f8
whats-next is a command published in the GitHub repository primeline-ai/evolving-lite (48 stars, last pushed 19d ago), licensed MIT. It adds 8 tokens to every session and 312 once invoked, about $0.0000 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 commands, from other repositories
my_brand
Interactive brand identity creation with archetypes, colors, typography, and voice guidelines. Use when user mentions "brand", "colors", "typography", "brand.md", "design system", or "visual identity".
my_commit
Create a well-formatted commit following project conventions (auto-detects Conventional Commits, Gitmoji, or Simple style).
my_research
Start comprehensive business research with market analysis, competitor intelligence, and idea validation.
my_tdd
Start Test-Driven Development workflow. Write failing tests first, then implement minimal code, then refactor.
my_docs
Update inline documentation and project docs for uncommitted changes.
my_review
Review uncommitted changes for bugs, security issues, code quality, and test coverage.