Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…
$ npx skills add petarzarkov/dunx --skill whats-next -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install petarzarkov/dunx whats-next --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/whats-next .claude/skills/whats-next && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "whats-next" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-next into .claude/skills/whats-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whats-next", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-nextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add petarzarkov/dunx --skill whats-next -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install petarzarkov/dunx whats-next --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/whats-next .agents/skills/whats-next && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "whats-next" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-next into .agents/skills/whats-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whats-next", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add petarzarkov/dunx --skill whats-next -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install petarzarkov/dunx whats-next --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/whats-next .cursor/skills/whats-next && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "whats-next" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-next into .cursor/skills/whats-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whats-next", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/petarzarkov/dunx.git --path .claude/skills/whats-next--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add petarzarkov/dunx --skill whats-next -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install petarzarkov/dunx whats-next --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/whats-next .gemini/skills/whats-next && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "whats-next" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-next into .gemini/skills/whats-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whats-next", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install petarzarkov/dunx whats-nextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add petarzarkov/dunx --skill whats-next -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/whats-next .github/skills/whats-next && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "whats-next" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-next into .github/skills/whats-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whats-next", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add petarzarkov/dunx --skill whats-next -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install petarzarkov/dunx whats-next --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petarzarkov/dunx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/whats-next .opencode/skills/whats-next && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "whats-next" agent skill from https://github.com/petarzarkov/dunx/tree/main/.claude/skills/whats-next into .opencode/skills/whats-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whats-next", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
whats-nextWrite or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…
Whats Next is an agent skill from petarzarkov/dunx. Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in docs/ROADMAP.md. Use before /compact or /clear, at the end of a task block, when the context window crosses ~50%, or when asked "what's next", "where were we", "hand this off", or "resume".
Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Context engineering. The repository describes itself as: fastest web DI framework. NestJS-style structure at Bun speed. Constructor DI with no reflect-metadata, no experimentalDecorators, no JavaScript router. The licence is MIT.
Read from SKILL.md and the folder at commit d8be36b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Whats Next loads about 819 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 369 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from petarzarkov/dunx at commit d8be36b, republished under its MIT licence (© petarzarkov). 369 words, ~819 tokens.
.claude/skills/whats-next/SKILL.md (or your agent's skills folder).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.
One batch, then stop:
git status --short && git log --oneline -8Read the Open items section of docs/ROADMAP.md and
the file under internal/notes/roadmap/ for the item in hand, when its row links
one. That is the source
of truth for what "next" means. 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 question and
ask each for a one-line verdict plus file:line. The exploration stays in their
context window; only the verdict comes back.
Overwrite HANDOFF.md with this shape. Omit a section that has no content -
never write "N/A" or "none".
# HANDOFF - <YYYY-MM-DD>
**Roadmap:** <open item> - <what remains of it>
**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>token() and
inject() to packages/core/src/di/, resolving through a module-level
currentInjector set around each new Klass()" - not "continue DI work".State the path and the roadmap position in one line, then name the next move:
/compact, and say explicitly what to preserve/clear, then continue from HANDOFF.mdHANDOFF.md is gitignored. It is session state, not a repo artifact - rewrite it
freely.
© petarzarkov, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/whats-next of petarzarkov/dunx.
Open the folder on GitHubat commit d8be36b
Whats Next next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Whats Next this skillpetarzarkov/dunx | 100 | — | ~819 | Automated safety check: Pass | MIT | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Memori Long-Term MemoryMemoriLabs/Memori | 17k | — | ~2k | Automated safety check: Notes | Custom licence | |
| Picoclaw Skill Creatorsipeed/picoclaw | 30k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Context Mode for Antigravity CLImksglu/context-mode | 26k | — | ~850 | Automated safety check: Pass | Custom licence | |
| ccc Semantic Code Searchcocoindex-io/cocoindex-code | 2.8k | — | ~938 | Automated safety check: Pass | Apache-2.0 |
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
sipeed/picoclaw
Guidance for creating, updating and reviewing Picoclaw skills, from the SKILL.md structure to organizing bundled scripts, references and assets.
mksglu/context-mode
Routing rules for using context-mode MCP tools in Antigravity CLI: sandboxed code runs, file analysis, indexed search and web fetches that keep large output out of the conversation.
cocoindex-io/cocoindex-code
Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.
alexgreensh/token-optimizer
Audits a Claude Code or Codex setup for context-window waste, fixes it with the user's approval, and measures the saving.
petarzarkov/dunx
Revise one documentation file so it states facts instead of performing insight, and get it under the budgets in scripts/no-slop.test.ts.
petarzarkov/dunx
Add a workspace to the dunx monorepo - a published package under packages/, a published CLI under tools/, a private workspace under internal/, or an example under examples/ - with correct manifest…
petarzarkov/dunx
Version and publish @dunx/ packages to npm. An agent skill from petarzarkov/dunx.
petarzarkov/dunx
Resolve an open technical question by measuring it on real Bun instead of assuming, then record the verified result in docs/architecture/constraints.md.
petarzarkov/dunx
Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%.
Categories
Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…. Whats Next is an agent skill from petarzarkov/dunx.md.
Whats Next fits situations like: tasks that involve Context engineering.
Run `npx skills add petarzarkov/dunx --skill whats-next -a claude-code`. Or copy the skill folder (.claude/skills/whats-next in petarzarkov/dunx) into .claude/skills/whats-next in your project. Claude Code loads it when a task matches its description.
Run `npx skills add petarzarkov/dunx --skill whats-next -a codex`. Or copy the skill folder (.claude/skills/whats-next in petarzarkov/dunx) into .agents/skills/whats-next in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add petarzarkov/dunx --skill whats-next -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/whats-next, .gemini/skills/whats-next, .github/skills/whats-next and .opencode/skills/whats-next in your project.
Going by SKILL.md and its folder, Whats Next needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Whats Next is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 819 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Whats Next: Context Mode Output Sandbox (mksglu/context-mode, 26k stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars), Picoclaw Skill Creator (sipeed/picoclaw, 30k stars) and Context Mode for Antigravity CLI (mksglu/context-mode, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
petarzarkov (a GitHub user) maintains it in petarzarkov/dunx, which has 100 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: petarzarkov/dunx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.