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…
Automatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics.
$ npx skills add ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ArabelaTso/Skills-4-SE code-instrumentation-generator --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/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/code-instrumentation-generator .claude/skills/code-instrumentation-generator && 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 "code-instrumentation-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generator into .claude/skills/code-instrumentation-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-instrumentation-generator", 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/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generatorType 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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ArabelaTso/Skills-4-SE code-instrumentation-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/code-instrumentation-generator .agents/skills/code-instrumentation-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-instrumentation-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generator into .agents/skills/code-instrumentation-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-instrumentation-generator", 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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ArabelaTso/Skills-4-SE code-instrumentation-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/code-instrumentation-generator .cursor/skills/code-instrumentation-generator && 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 "code-instrumentation-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generator into .cursor/skills/code-instrumentation-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-instrumentation-generator", 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/ArabelaTso/Skills-4-SE.git --path skills/code-instrumentation-generator--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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ArabelaTso/Skills-4-SE code-instrumentation-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/code-instrumentation-generator .gemini/skills/code-instrumentation-generator && 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 "code-instrumentation-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generator into .gemini/skills/code-instrumentation-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-instrumentation-generator", 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 ArabelaTso/Skills-4-SE code-instrumentation-generatorInstalls 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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/code-instrumentation-generator .github/skills/code-instrumentation-generator && 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 "code-instrumentation-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generator into .github/skills/code-instrumentation-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-instrumentation-generator", 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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ArabelaTso/Skills-4-SE code-instrumentation-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/code-instrumentation-generator .opencode/skills/code-instrumentation-generator && 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 "code-instrumentation-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/code-instrumentation-generator into .opencode/skills/code-instrumentation-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-instrumentation-generator", 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.
code-instrumentation-generatorAutomatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics.
Code Instrumentation Generator is an agent skill from ArabelaTso/Skills-4-SE. Automatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics. Use when users need to: (1) Add logging or tracing to code for debugging, (2) Collect runtime execution data for analysis, (3) Monitor function calls and control flow, (4) Track variable values during execution, (5) Generate execution traces for testing or profiling. Supports Python, Java, JavaScript, and C/C++ with…
Its SKILL.md is about 2.3k 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. It works with C++, Java, JavaScript and Python. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4f38503. 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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python, java, javascript, c and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
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.
Code Instrumentation Generator loads about 2.3k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 386 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 ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 386 words, ~2,290 tokens.
.claude/skills/code-instrumentation-generator/SKILL.md (or your agent's skills folder).Automatically instrument source code to collect runtime information while preserving program semantics.
Follow these steps to instrument code:
Understand the code structure and identify instrumentation points:
Choose appropriate instrumentation based on requirements:
Instrumentation levels:
Configuration options:
Add instrumentation hooks at identified points:
Function instrumentation:
Branch instrumentation:
Variable instrumentation:
Verify that instrumentation doesn't change program behavior:
Provide instrumented code and documentation:
# Original code
def calculate_sum(a, b):
result = a + b
return result
# Instrumented code
import logging
logging.basicConfig(level=logging.INFO)
def calculate_sum(a, b):
# Function entry instrumentation
logging.info(f"ENTER calculate_sum(a={a}, b={b})")
result = a + b
# Variable instrumentation
logging.info(f"VAR result={result}")
# Function exit instrumentation
logging.info(f"EXIT calculate_sum() -> {result}")
return result// Original code
public int calculateSum(int a, int b) {
int result = a + b;
return result;
}
// Instrumented code
public int calculateSum(int a, int b) {
// Function entry instrumentation
System.out.println("ENTER calculateSum(a=" + a + ", b=" + b + ")");
int result = a + b;
// Variable instrumentation
System.out.println("VAR result=" + result);
// Function exit instrumentation
System.out.println("EXIT calculateSum() -> " + result);
return result;
}// Original code
function calculateSum(a, b) {
const result = a + b;
return result;
}
// Instrumented code
function calculateSum(a, b) {
// Function entry instrumentation
console.log(`ENTER calculateSum(a=${a}, b=${b})`);
const result = a + b;
// Variable instrumentation
console.log(`VAR result=${result}`);
// Function exit instrumentation
console.log(`EXIT calculateSum() -> ${result}`);
return result;
}// Original code
int calculate_sum(int a, int b) {
int result = a + b;
return result;
}
// Instrumented code
#include <stdio.h>
int calculate_sum(int a, int b) {
// Function entry instrumentation
printf("ENTER calculate_sum(a=%d, b=%d)\n", a, b);
int result = a + b;
// Variable instrumentation
printf("VAR result=%d\n", result);
// Function exit instrumentation
printf("EXIT calculate_sum() -> %d\n", result);
return result;
}# Original code
def check_value(x):
if x > 0:
return "positive"
else:
return "non-positive"
# Instrumented code
def check_value(x):
logging.info(f"ENTER check_value(x={x})")
# Branch instrumentation
if x > 0:
logging.info("BRANCH if(x > 0) -> TRUE")
result = "positive"
else:
logging.info("BRANCH if(x > 0) -> FALSE")
result = "non-positive"
logging.info(f"EXIT check_value() -> {result}")
return resultGenerate a configuration file to control instrumentation:
# instrumentation_config.py
INSTRUMENTATION_ENABLED = True
INSTRUMENT_FUNCTIONS = True
INSTRUMENT_BRANCHES = True
INSTRUMENT_VARIABLES = False
LOG_LEVEL = "INFO"
OUTPUT_FORMAT = "text" # or "json", "csv"
# Instrumented code with configuration
import instrumentation_config as config
def calculate_sum(a, b):
if config.INSTRUMENT_FUNCTIONS:
logging.info(f"ENTER calculate_sum(a={a}, b={b})")
result = a + b
if config.INSTRUMENT_VARIABLES:
logging.info(f"VAR result={result}")
if config.INSTRUMENT_FUNCTIONS:
logging.info(f"EXIT calculate_sum() -> {result}")
return result## Instrumentation Report
**File**: calculator.py
**Instrumentation Date**: 2024-02-17
**Configuration**: Function-level + Branch-level
### Instrumented Functions
1. **calculate_sum(a, b)**
- Entry probe: Line 3
- Exit probe: Line 8
- Captures: Parameters (a, b), return value
2. **check_value(x)**
- Entry probe: Line 11
- Branch probe: Line 14 (if x > 0)
- Exit probe: Line 19
- Captures: Parameter (x), branch decision, return value
### Instrumentation Statistics
- Total functions instrumented: 2
- Total branches instrumented: 1
- Total variables instrumented: 0
- Estimated overhead: <5%
### Usage
Run the instrumented code normally. Instrumentation output will be written to:
- Console (stdout)
- Log file: instrumentation.log (if configured)# Only instrument specific functions
INSTRUMENTED_FUNCTIONS = ["calculate_sum", "process_data"]
def should_instrument(func_name):
return func_name in INSTRUMENTED_FUNCTIONS
# Apply instrumentation conditionally
if should_instrument("calculate_sum"):
# Add instrumentation
passimport time
def calculate_sum(a, b):
start_time = time.time()
logging.info(f"ENTER calculate_sum(a={a}, b={b})")
result = a + b
elapsed = time.time() - start_time
logging.info(f"EXIT calculate_sum() -> {result} [time={elapsed:.6f}s]")
return resultimport json
import time
def calculate_sum(a, b):
entry_event = {
"type": "function_entry",
"function": "calculate_sum",
"params": {"a": a, "b": b},
"timestamp": time.time()
}
print(json.dumps(entry_event))
result = a + b
exit_event = {
"type": "function_exit",
"function": "calculate_sum",
"return_value": result,
"timestamp": time.time()
}
print(json.dumps(exit_event))
return result© ArabelaTso, Apache-2.0. 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 skills/code-instrumentation-generator of ArabelaTso/Skills-4-SE.
Open the folder on GitHubat commit 4f38503
Code Instrumentation Generator 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 |
|---|---|---|---|---|---|---|
| Code Instrumentation Generator this skillArabelaTso/Skills-4-SE | 253 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Debuggerdebugmcp/mcp-debugger | 171 | — | ~3.8k | Automated safety check: Pass | MIT | |
| CodeQL Security Scantrailofbits/skills | 7.4k | — | ~4.6k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Fory Version Bumpapache/fory | 4.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Fory Performance Optimizationapache/fory | 4.6k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Constant-Time Analysistrailofbits/skills | 7.4k | — | ~3.3k | Automated safety check: Notes | CC-BY-SA-4.0 |
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…
trailofbits/skills
Scans a codebase for vulnerabilities with CodeQL's data flow and taint tracking in run-all or important-only modes, including data extensions for project-specific sources and sinks.
apache/fory
Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C, Dart, JavaScript, Swift, integration tests, examples, and source docs.
apache/fory
Run profile-driven bottleneck optimization across Apache Fory implementations (Java, C++, Python/Cython, Go, Rust, Swift, C, JavaScript/TypeScript, Dart, Kotlin, Scala).
trailofbits/skills
Compiles cryptographic code and inspects the assembly or bytecode for variable-time instructions, then triages which flagged operations actually touch secrets.
apache/fory
Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.
ArabelaTso/Skills-4-SE
Generate prioritized CVE watchlists and actionable security recommendations for repositories.
ArabelaTso/Skills-4-SE
Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).
ArabelaTso/Skills-4-SE
Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.
ArabelaTso/Skills-4-SE
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.
ArabelaTso/Skills-4-SE
Automatically migrate Spring MVC applications to Spring Boot.
ArabelaTso/Skills-4-SE
Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.
Works with
Categories
Automatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics. Code Instrumentation Generator is an agent skill from ArabelaTso/Skills-4-SE. Automatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics.
Code Instrumentation Generator fits situations like: tracing to code for debugging; collect runtime execution data for analysis; monitor function calls and control flow; track variable values during execution.
Run `npx skills add ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a claude-code`. Or copy the skill folder (skills/code-instrumentation-generator in ArabelaTso/Skills-4-SE) into .claude/skills/code-instrumentation-generator in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a codex`. Or copy the skill folder (skills/code-instrumentation-generator in ArabelaTso/Skills-4-SE) into .agents/skills/code-instrumentation-generator 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 ArabelaTso/Skills-4-SE --skill code-instrumentation-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-instrumentation-generator, .gemini/skills/code-instrumentation-generator, .github/skills/code-instrumentation-generator and .opencode/skills/code-instrumentation-generator in your project.
SKILL.md names no scripts, command-line tools or credentials: Code Instrumentation Generator is instructions for the agent only. Our summary lists: Python 3.
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.
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.
Code Instrumentation Generator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.2k 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 Code Instrumentation Generator: MCP Debugger (debugmcp/mcp-debugger, 171 stars), CodeQL Security Scan (trailofbits/skills, 7.4k stars), Fory Version Bump (apache/fory, 4.6k stars) and Fory Performance Optimization (apache/fory, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 151 skills in this directory. The repository was last updated on August 21, 2026.
Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.