MCP Debugger
debugmcp/mcp-debugger
A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…
Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox.
Install Okojo Node Ink Debug
$ npx skills add akeit0/okojo --skill okojo-node-ink-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install akeit0/okojo okojo-node-ink-debug --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/akeit0/okojo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/okojo-node-ink-debug .claude/skills/okojo-node-ink-debug && 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 "okojo-node-ink-debug" agent skill from https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debug into .claude/skills/okojo-node-ink-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "okojo-node-ink-debug", 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/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debugType 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 akeit0/okojo --skill okojo-node-ink-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install akeit0/okojo okojo-node-ink-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akeit0/okojo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/okojo-node-ink-debug .agents/skills/okojo-node-ink-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "okojo-node-ink-debug" agent skill from https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debug into .agents/skills/okojo-node-ink-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "okojo-node-ink-debug", 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 akeit0/okojo --skill okojo-node-ink-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install akeit0/okojo okojo-node-ink-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akeit0/okojo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/okojo-node-ink-debug .cursor/skills/okojo-node-ink-debug && 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 "okojo-node-ink-debug" agent skill from https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debug into .cursor/skills/okojo-node-ink-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "okojo-node-ink-debug", 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/akeit0/okojo.git --path .agents/skills/okojo-node-ink-debug--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 akeit0/okojo --skill okojo-node-ink-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install akeit0/okojo okojo-node-ink-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akeit0/okojo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/okojo-node-ink-debug .gemini/skills/okojo-node-ink-debug && 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 "okojo-node-ink-debug" agent skill from https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debug into .gemini/skills/okojo-node-ink-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "okojo-node-ink-debug", 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 akeit0/okojo okojo-node-ink-debugInstalls 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 akeit0/okojo --skill okojo-node-ink-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/akeit0/okojo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/okojo-node-ink-debug .github/skills/okojo-node-ink-debug && 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 "okojo-node-ink-debug" agent skill from https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debug into .github/skills/okojo-node-ink-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "okojo-node-ink-debug", 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 akeit0/okojo --skill okojo-node-ink-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install akeit0/okojo okojo-node-ink-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akeit0/okojo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/okojo-node-ink-debug .opencode/skills/okojo-node-ink-debug && 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 "okojo-node-ink-debug" agent skill from https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-node-ink-debug into .opencode/skills/okojo-node-ink-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "okojo-node-ink-debug", 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.
Facts
- Skill name
okojo-node-ink-debug- GitHub stars
- 160
- Token cost
- ~798 tokens
- SKILL.md length
- 312 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox.
- Works in 4 steps: correctness → observability/tooling → focused compatibility increments → …
- Tasks that involve Debugging
- SKILL.md covers Primary goal, Core policy, Required workflow and Required tools, plus 3 more sections
- Calls dotnet
What it does
Okojo Node Ink Debug is an agent skill from akeit0/okojo. Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox. Use this for Ink bring-up, reduced Okojo.Node repros, CommonJS/ESM/runtime compatibility debugging, debugger/disassembly investigation, and focused regression-driven fixes.
Its SKILL.md is about 800 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 Development, covering Debugging. It works with C#, JavaScript and .NET. The repository describes itself as: Okojo is an experimental low allocation managed JavaScript engine for .NET. The licence is MIT.
When your agent uses it
- Tasks that involve Debugging
Example prompts
- “/okojo-node-ink-debug”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- correctness
- observability/tooling
- focused compatibility increments
- measured optimization
What it can do on your machine
Read from SKILL.md and the folder at commit 478ec2d. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
dotnet
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Okojo Node Ink Debug loads about 798 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 312 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from akeit0/okojo at commit 478ec2d, republished under its MIT licence (© akeit0). 312 words, ~798 tokens.
Download SKILL.mdSave it as
.claude/skills/okojo-node-ink-debug/SKILL.md (or your agent's skills folder).- name
- okojo-node-ink-debug
- description
- Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox. Use this for Ink bring-up, reduced Okojo.Node repros, CommonJS/ESM/runtime compatibility debugging, debugger/disassembly investigation, and focused regression-driven fixes.
Okojo.Node Ink Debug
Use this skill for work under:
sandbox\OkojoInkProbesandbox\OkojoNodeDebugSandboxsrc\Okojo.Nodesrc\Okojotests\Okojo.Node.Testsdocs\PALE_NODE_INK_DEBUG_WORKFLOW.md
Primary goal
Move sandbox\OkojoInkProbe forward by fixing real engine/runtime/compiler bugs and missing compatibility surfaces in a disciplined order.
Prefer:
- correctness
- observability/tooling
- focused compatibility increments
- measured optimization
Core policy
Do not treat large-app failures as app-specific until reduction proves they are.
Prefer:
- Node as the reference for Node-facing behavior
- V8 / Node bytecode behavior when the failure looks compiler/VM related
Avoid:
- broad speculative fixes
- Ink-specific hacks for general runtime/compiler bugs
- skipping the reduction step when a smaller repro is possible
Required workflow
- reproduce in
sandbox\OkojoInkProbe - reduce to the smallest JS shape possible
- move the reduced shape into
tests\Okojo.Node.Testswhen stable - inspect disassembly / debugger state in
sandbox\OkojoNodeDebugSandbox - compare with Node behavior
- implement the narrow fix
- rerun focused regressions
- rerun Ink to reveal the next blocker
Read:
docs\PALE_NODE_INK_DEBUG_WORKFLOW.md
before doing substantial work in this area.
Required tools
Real integration checkpoint
dotnet run --project sandbox\OkojoInkProbe\OkojoInkProbe.csproj -c Release -- --debuggerFocused debugger sandbox
dotnet run --project sandbox\OkojoNodeDebugSandbox\OkojoNodeDebugSandbox.csproj -c Release -- --app-root <appRoot> --entry <entry> --stop caught --log <logPath>Use the focused debugger sandbox for:
debugger;stops- caught exceptions
- disassembly around the current PC
- locals/register inspection
- reduced app repros
Testing loop
Focused loop:
dotnet test tests\Okojo.Node.Tests\Okojo.Node.Tests.csproj -c Release --filter <Name>After a fix, rerun nearby focused regressions before going back to Ink.
If the change becomes broad or touches shared compiler/runtime paths, expand validation appropriately.
Current known lessons
- the old Ink
require(undefined)failure was actually a wide-register compiler bug - dedicated debugger/disassembly tooling was necessary to prove the root cause
AbortControllersupport may be needed tactically for bring-up, butAbort*/Event*likely belong long-term inOkojo.WebPlatform/ shared web globals
Deliverables expected from this skill
When using this skill, aim to leave behind:
- a reduced repro
- a focused regression test
- a narrow code fix
- a rerun of Ink showing either success or the next blocker
If the blocker changes, update the workflow note or the active session plan so other agents can resume cleanly.
© akeit0, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/okojo-node-ink-debug of akeit0/okojo.
Open the folder on GitHubat commit 478ec2d
Compare with similar skills
Okojo Node Ink Debug 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 |
|---|---|---|---|---|---|---|
| Okojo Node Ink Debug this skillakeit0/okojo | 160 | — | ~798 | Automated safety check: Pass | MIT | |
| MCP Debuggerdebugmcp/mcp-debugger | 171 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Git HooksProrise-cool/Claude-Code-Multi-Agent | 305 | — | ~3.6k | Automated safety check: Notes | None | |
| Dotnet Advisornovotnyllc/dotnet-artisan | 233 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Corvus Typescript Evaluatorcorvus-dotnet/Corvus.JsonSchema | 199 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Sentry Fix Stack Tracesgetsentry/sentry-for-ai | 268 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Git Hooks
Prorise-cool/Claude-Code-Multi-Agent
Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.
Dotnet Advisor
novotnyllc/dotnet-artisan
Routes .NET/C requests to the correct domain skill and loads coding standards as baseline for all code paths.
Corvus Typescript Evaluator
corvus-dotnet/Corvus.JsonSchema
Work on the TypeScript port of the V5 standalone schema evaluator (src-ts/corvus-json-schema, npm package @corvus-dotnet/json-schema): loader, compiler, JavaScript code generator, results collector…
- Official
Sentry Fix Stack Traces
getsentry/sentry-for-ai
Make Sentry stack traces readable — upload source maps for JavaScript/TypeScript, or debug files for native and mobile (dSYM, ProGuard/R8, NDK symbols, Dart obfuscation maps, .NET PDBs).
Sokol Net
elix22/Sokol.NET
Sokol.NET framework development — use for ANY work in this repo: creating or debugging examples, building/running for desktop/Android/iOS/Web, writing or compiling shaders, adding a new C/C++…
More from akeit0/okojo
Okojo Test262
akeit0/okojo
Run and continue Okojo Test262 compliance work. An agent skill from akeit0/okojo.
Okojo Engine Development
akeit0/okojo
Develop or debug Okojo ECMAScript engine internals. An agent skill from akeit0/okojo.
Related
Works with
Categories
Questions about Okojo Node Ink Debug
What does Okojo Node Ink Debug do?
Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox. Okojo Node Ink Debug is an agent skill from akeit0/okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox.
When should I use Okojo Node Ink Debug?
Okojo Node Ink Debug fits situations like: tasks that involve Debugging.
How do I install Okojo Node Ink Debug in Claude Code?
Run `npx skills add akeit0/okojo --skill okojo-node-ink-debug -a claude-code`. Or copy the skill folder (.agents/skills/okojo-node-ink-debug in akeit0/okojo) into .claude/skills/okojo-node-ink-debug in your project. Claude Code loads it when a task matches its description.
How do I install Okojo Node Ink Debug in Codex?
Run `npx skills add akeit0/okojo --skill okojo-node-ink-debug -a codex`. Or copy the skill folder (.agents/skills/okojo-node-ink-debug in akeit0/okojo) into .agents/skills/okojo-node-ink-debug in your project. Codex loads it when a task matches its description.
Can I use Okojo Node Ink Debug in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akeit0/okojo --skill okojo-node-ink-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/okojo-node-ink-debug, .gemini/skills/okojo-node-ink-debug, .github/skills/okojo-node-ink-debug and .opencode/skills/okojo-node-ink-debug in your project.
What does Okojo Node Ink Debug need to run?
Going by SKILL.md and its folder, Okojo Node Ink Debug needs the command-line tools its instructions call (dotnet).
Does Okojo Node Ink Debug access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Okojo Node Ink Debug safe to install?
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.
What licence does Okojo Node Ink Debug use?
Okojo Node Ink Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Okojo Node Ink Debug use?
About 798 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Okojo Node Ink Debug?
Skills that share tags, products or a category with Okojo Node Ink Debug: MCP Debugger (debugmcp/mcp-debugger, 171 stars), Git Hooks (Prorise-cool/Claude-Code-Multi-Agent, 305 stars), Dotnet Advisor (novotnyllc/dotnet-artisan, 233 stars) and Corvus Typescript Evaluator (corvus-dotnet/Corvus.JsonSchema, 199 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Okojo Node Ink Debug?
akeit0 (a GitHub user) maintains it in akeit0/okojo, which has 160 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 21, 2026.
Source: akeit0/okojo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.