Debug
asgeirtj/system_prompts_leaks
Enable debug logging for this session and help diagnose issues
Investigate CodSpeed CI performance reports on PRs — regressions or improbable improvements that don't reproduce locally.
MITAuto-check passed
Install Codspeed Debug
$ npx skills add cometkim/unicode-segmenter --skill codspeed-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cometkim/unicode-segmenter codspeed-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/cometkim/unicode-segmenter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/codspeed-debug .claude/skills/codspeed-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 "codspeed-debug" agent skill from https://github.com/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-debug into .claude/skills/codspeed-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codspeed-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/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-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 cometkim/unicode-segmenter --skill codspeed-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cometkim/unicode-segmenter codspeed-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cometkim/unicode-segmenter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/codspeed-debug .agents/skills/codspeed-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 "codspeed-debug" agent skill from https://github.com/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-debug into .agents/skills/codspeed-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codspeed-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 cometkim/unicode-segmenter --skill codspeed-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cometkim/unicode-segmenter codspeed-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cometkim/unicode-segmenter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/codspeed-debug .cursor/skills/codspeed-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 "codspeed-debug" agent skill from https://github.com/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-debug into .cursor/skills/codspeed-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codspeed-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/cometkim/unicode-segmenter.git --path .claude/skills/codspeed-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 cometkim/unicode-segmenter --skill codspeed-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cometkim/unicode-segmenter codspeed-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cometkim/unicode-segmenter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/codspeed-debug .gemini/skills/codspeed-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 "codspeed-debug" agent skill from https://github.com/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-debug into .gemini/skills/codspeed-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codspeed-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 cometkim/unicode-segmenter codspeed-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 cometkim/unicode-segmenter --skill codspeed-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cometkim/unicode-segmenter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/codspeed-debug .github/skills/codspeed-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 "codspeed-debug" agent skill from https://github.com/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-debug into .github/skills/codspeed-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codspeed-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 cometkim/unicode-segmenter --skill codspeed-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 cometkim/unicode-segmenter codspeed-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cometkim/unicode-segmenter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/codspeed-debug .opencode/skills/codspeed-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 "codspeed-debug" agent skill from https://github.com/cometkim/unicode-segmenter/tree/main/.claude/skills/codspeed-debug into .opencode/skills/codspeed-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codspeed-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
codspeed-debug- GitHub stars
- 112
- Token cost
- ~814 tokens
- SKILL.md length
- 426 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Investigate CodSpeed CI performance reports on PRs — regressions or improbable improvements that don't reproduce locally.
- The CodSpeed check flags a delta and you need to replicate
- SKILL.md covers How the instrumented…, Local replication recipe and Other V8 behaviors that have…
- Calls node
What it does
Codspeed Debug is an agent skill from cometkim/unicode-segmenter. Investigate CodSpeed CI performance reports on PRs — regressions or improbable improvements that don't reproduce locally. Use when the CodSpeed check flags a delta and you need to replicate or explain it.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A lightweight implementation of the Unicode Text Segmentation (UAX 29). The licence is MIT.
When your agent uses it
- The CodSpeed check flags a delta and you need to replicate
Example prompts
- “/codspeed-debug”
What it can do on your machine
Read from SKILL.md and the folder at commit 5d3c738. 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:
node
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
Codspeed Debug loads about 814 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 426 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 cometkim/unicode-segmenter at commit 5d3c738, republished under its MIT licence (© cometkim). 426 words, ~814 tokens.
Download SKILL.mdSave it as
.claude/skills/codspeed-debug/SKILL.md (or your agent's skills folder).- name
- codspeed-debug
- description
- Investigate CodSpeed CI performance reports on PRs — regressions or improbable improvements that don't reproduce locally. Use when the CodSpeed check flags a delta and you need to replicate or explain it.
Debugging CodSpeed results
CI (.github/workflows/codspeed.yml) runs node benchmark/grapheme/codspeed.js (tinybench + @codspeed/tinybench-plugin) under CodSpeedHQ/action in simulation mode: a valgrind-style instrumented VM counting simulated CPU work, not wall clock. Its numbers routinely disagree with mitata.
How the instrumented measurement differs from mitata
- V8 runs with stability flags (e.g.
--predictable --hash-seed=1) and the plugin measures roughly: a few warmup calls → forcedgc()→ one measured call. - Consequence 1: the measured call sees whatever tier the code reached during warmup. The repo defends with a 2000-iteration
beforeAllwarmup incodspeed.js— do not remove it. - Consequence 2 (the big trap): forced GC clears weak references embedded in optimized code (deopt reason:
embedded weak objects cleared— e.g. hidden-class maps of objects with no live instances), so optimized code deopts right before the measured call, producing phantom regressions up to ~60%.src/grapheme.jscarried a defense against this from #133 to #145: a block stashing a live generator and its first result onPAIR._keep, so the segment-object hidden classes stayed strongly reachable across GC. It was removed after measuring it inert on the current (generator-based) code — the deopt it guarded was diagnosed on a class-iterator rewrite that never shipped. If you re-add anything like it, note that a module-scopeconst _keep = ...does NOT work: unreferenced module bindings don't survive module evaluation, so the pin has to hang off an object that stays reachable.- Before re-adding it, measure it properly: a single instrumented call cannot resolve this for
graphemeSegments, which allocates ~120 objects per call, so whether a scavenge lands inside the measured call swings it ±30%. Run 50{ gc(); one call }cycles under callgrind and subtract a{ gc() }-only run of the same shape; that showed 92,965 vs 92,915 instructions per call (0.05%), with the pin making each major GC ~26 k instructions more expensive.
Show full SKILL.md (131 more words)Show less
Local replication recipe
Write a scratch script that mimics the protocol per case: N warmup calls, globalThis.gc(), then time exactly one call. Run with:
node --expose-gc --predictable --hash-seed=1 scratch.mjsDiagnose tiering with --trace-deopt, --trace-opt, and --trace-baseline; a deopt logged between the gc() and the measured call is the smoking gun.
Other V8 behaviors that have bitten this repo
- Sparkplug (baseline) compiles in batches with a ~4 KiB source-length threshold: one huge function can be compiled alone or later than the same logic split into smaller functions, so pure source-size changes can shift tier-up timing and show up as CodSpeed deltas unrelated to algorithmic cost.
- Deltas under ~5% in simulation mode are noise. Before reacting to anything, open the flame diff on codspeed.io and check whether the changed frames are in the segmenter or in the harness/GC.
© cometkim, 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 .claude/skills/codspeed-debug of cometkim/unicode-segmenter.
Open the folder on GitHubat commit 5d3c738
Compare with similar skills
Codspeed 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 |
|---|---|---|---|---|---|---|
| Codspeed Debug this skillcometkim/unicode-segmenter | 112 | — | ~814 | Automated safety check: Pass | MIT | |
| Debugasgeirtj/system_prompts_leaks | 69k | — | ~439 | Automated safety check: Pass | CC0-1.0 | |
| Root Cause Investigationgarrytan/gstack | 136k | — | ~12k | Automated safety check: Notes | MIT | |
| Runtime Debugvercel/next.js | 143k | 1 repos | ~618 | Automated safety check: Pass | MIT | |
| Openclaw Debuggingopenclaw/openclaw | 392k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence |
Similar skills
Root Cause Investigation
garrytan/gstack
Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.
- Official
Runtime Debug
vercel/next.js
Debug and verification workflow for runtime-bundle and module-resolution regressions.
Openclaw Debugging
openclaw/openclaw
Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Debugging Toolkit
sickn33/agentic-awesome-skills
A skill your agent uses when working with debugging toolkit smart debug (Alias for debugging-toolkit-smart-debug)
More from cometkim/unicode-segmenter
Bench Records
cometkim/unicode-segmenter
Archive benchmark runs into benchmark/grapheme/records and regenerate the HTML report.
Benchmark
cometkim/unicode-segmenter
Measure runtime perf, bundle size, and memory impact of unicode-segmenter changes.
Unicode Data
cometkim/unicode-segmenter
Regenerate the generated Unicode data modules (src/graphemedata.js, generaldata.js, emojidata.js, test/unicodetestdata.js) and verify correctness.
Questions about Codspeed Debug
What does Codspeed Debug do?
Investigate CodSpeed CI performance reports on PRs — regressions or improbable improvements that don't reproduce locally. Codspeed Debug is an agent skill from cometkim/unicode-segmenter. Investigate CodSpeed CI performance reports on PRs — regressions or improbable improvements that don't reproduce locally.
When should I use Codspeed Debug?
Codspeed Debug fits situations like: the CodSpeed check flags a delta and you need to replicate.
How do I install Codspeed Debug in Claude Code?
Run `npx skills add cometkim/unicode-segmenter --skill codspeed-debug -a claude-code`. Or copy the skill folder (.claude/skills/codspeed-debug in cometkim/unicode-segmenter) into .claude/skills/codspeed-debug in your project. Claude Code loads it when a task matches its description.
How do I install Codspeed Debug in Codex?
Run `npx skills add cometkim/unicode-segmenter --skill codspeed-debug -a codex`. Or copy the skill folder (.claude/skills/codspeed-debug in cometkim/unicode-segmenter) into .agents/skills/codspeed-debug in your project. Codex loads it when a task matches its description.
Can I use Codspeed 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 cometkim/unicode-segmenter --skill codspeed-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/codspeed-debug, .gemini/skills/codspeed-debug, .github/skills/codspeed-debug and .opencode/skills/codspeed-debug in your project.
What does Codspeed Debug need to run?
Going by SKILL.md and its folder, Codspeed Debug needs the command-line tools its instructions call (node).
Does Codspeed 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 Codspeed 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 Codspeed Debug use?
Codspeed 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 Codspeed Debug use?
About 814 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.
What are the alternatives to Codspeed Debug?
Skills that share tags, products or a category with Codspeed Debug: Debug (asgeirtj/system_prompts_leaks, 69k stars), Root Cause Investigation (garrytan/gstack, 136k stars), Runtime Debug (vercel/next.js, 143k stars) and Openclaw Debugging (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Codspeed Debug?
cometkim (a GitHub user) maintains it in cometkim/unicode-segmenter, which has 112 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 29, 2026.
Source: cometkim/unicode-segmenter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.