Borrowing it
Nothing to install: this file belongs to petarzarkov/dunx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/petarzarkov/dunx/main/.claude/skills/whats-next/SKILL.mdgit clone --depth 1 https://github.com/petarzarkov/dunxWrote 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/petarzarkov/dunx/whats-next)<a href="https://agentmods.dev/skills/petarzarkov/dunx/whats-next"><img src="https://agentmods.dev/badge/skills/petarzarkov/dunx/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.
<a href="https://agentmods.dev/skills/petarzarkov/dunx/whats-next"><img src="https://agentmods.dev/badge/skills/petarzarkov/dunx/whats-next.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.00092 | $0.00837 |
| Opus 5 | $0.00046 | $0.00418 |
| Sonnet 5 | $0.00018 | $0.00167 |
| Haiku 4.5 | $0.00009 | $0.00084 |
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 11d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/whats-next
Produce HANDOFF.md at the repo root: everything needed to resume this work in a
fresh session and nothing else. It will be read cold, by a session with no
memory of this one. Optimise for that reader, not for a record of what happened.
Gather
One batch, then stop:
git status --short && git log --oneline -8
Read the Roadmap and Spikes to resolve sections of docs/ARCHITECTURE.md. That doc is the source of truth for what "next" means - the current phase's exit criteria are the next steps. Never invent a roadmap position from the conversation.
Add what only this session knows: what you actually changed, and what you tried that did not work.
If the session is thin on state - resumed, compacted, or you were handed a
HANDOFF.md rather than doing the work - do not read packages into this thread to
fill the gaps. Delegate one Explore subagent per unresolved exit criterion and
ask each for a one-line verdict plus file:line. The exploration stays in their
context window; only the verdict comes back.
Write
Overwrite HANDOFF.md with this shape. Omit a section that has no content -
never write "N/A" or "none".
# HANDOFF - <YYYY-MM-DD>
**Roadmap:** Phase <n> - <name> · <met>/<total> exit criteria met
**Branch:** <branch> @ <short sha> · <clean | n files dirty>
## Done
- <objective> - <where it landed>
## Live files
- [path](path) - <what is half-finished in it>
## Rejected - do not retry
- <approach> - <what broke>
## Next
1. <exact command, or exact edit to an exact path>
## Open questions
- <question> - <what decides it>
Rules
- Hard cap ~60 lines. This file is loaded at the start of the next session. Every line is a permanent tax on it.
- Next steps are commands and edits, not intentions. "Add
token()andinject()topackages/core/src/di/, resolving through a module-levelcurrentInjectorset around eachnew Klass()" - not "continue DI work". - Rejected is the highest-value section. It is the only content a fresh session cannot re-derive from the tree. Record the approach, the symptom, and the path it lives or lived in. Rejections already written down in docs/architecture/ belong there, not here - link, don't copy.
- Paths as clickable relative markdown links.
- If an exit criterion has become true, say so. If docs/ARCHITECTURE.md is stale, fix that doc - do not record the drift in HANDOFF.md.
- No conversation summary, no restatement of the plan, no preamble.
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.
- 11d ago First seen · 91 lines · 92 tokens per session scan A 3b270639c135
whats-next is a skill published in the GitHub repository petarzarkov/dunx (116 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 837 once invoked, about $0.0005 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
nestjs
Use when building or structuring a NestJS backend — feature modules, providers and DI wiring, provider scopes and request-lifecycle order, where to bind guards/pipes/interceptors/filters, and testing with Test.createTestingModule. NOT a bare Express/Fastify service with no DI (that is nodejs), NOT framework-agnostic…
query-kb
Load scoped repository context, then search and navigate a hraness/kb Markdown vault with hybrid text retrieval, exact metadata, bounded links and typed relationships, backlinks, whole-vault graph reports, and optional Git provenance. Use when an agent needs the applicable repository instructions, rationale, prior…
percolate-kb
Review a hraness/kb Markdown vault for recurring ideas and missing structural connections, then promote evidence-backed concepts and typed relationships with the KB CLI. Use after materially adding or revising notes, when organizing an accumulated vault, or when an agent needs to turn repeated tags and prose…
refresh-kb
Refresh and validate a hraness/kb Markdown knowledge graph after notes, concepts, typed relationships, attachments, repository scopes, or context mappings change. Use when an agent needs to maintain a managed or authored catalog, inspect graph and lifecycle findings, validate local artifacts and scope hubs, or…
nestjs-expert
Expert knowledge in NestJS framework, modular architecture, dependency injection, TypeORM/Prisma persistence, microservices transports, and enterprise-grade Node.js backend development. Use when the user mentions NestJS, Nest CLI, decorators, dependency injection, guards, interceptors, or backend microservices, or…
remember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture…