What is Debug Snapshot?

A diagnostic skill that records the computer’s environment, current working folder, recent Git activity, open network ports, and resource state. Git is a tool for tracking changes to code.

Use it to capture a factual snapshot of the machine and project when debugging build or deployment problems. It also shows recent file changes, recent commits, listeners, memory, disk, and related system details.

It helps reveal issues such as the wrong folder, an unavailable command, unset environment variables, stale files, a dirty worktree, or limited disk space before suggesting a fix.

Debug Snapshot — Skill for Claude Code by CocoRoF/geny-executor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add CocoRoF/geny-executor --skill debug

Clone the repo

git clone --depth 1 https://github.com/CocoRoF/geny-executor

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cocorof/geny-executor/debug/github.svg)](https://agentmods.dev/skills/cocorof/geny-executor/debug)

Your own site

<a href="https://agentmods.dev/skills/cocorof/geny-executor/debug"><img src="https://agentmods.dev/badge/skills/cocorof/geny-executor/debug/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cocorof/geny-executor/debug"><img src="https://agentmods.dev/badge/skills/cocorof/geny-executor/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 835 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00034	$0.00835
Opus 5.5	$0.00014	$0.00334
Sonnet 5.5	$0.00007	$0.00167
Haiku 4.5	$0.00003	$0.00084

Measured 1mo ago against content hash c907a10c41b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Debug Snapshot 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 1mo 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.

src/geny_executor/skills/bundled/debug/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debug — host + session diagnostic snapshot

The captured snapshot below is the ground truth. Read it carefully before suggesting any fix — many "obvious" fixes are wrong because the bug is one layer up (wrong PATH, wrong cwd, stale lock file, unset env var, dirty worktree).

Identity

User: !id -un
Groups: !id -Gn
Hostname: !hostname
Uptime: !uptime

Filesystem context

cwd: !pwd
cwd writable?: ![ -w "$(pwd)" ] && echo yes || echo no
Disk free (cwd): !df -h "$(pwd)" 2>/dev/null | tail -n 1 || echo "(df failed)"
Inode pressure: !df -i "$(pwd)" 2>/dev/null | tail -n 1 || echo "(df failed)"

Recently-touched files (last 5 minutes, current tree)

find . -maxdepth 3 -type f -mmin -5 -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/__pycache__/*" 2>/dev/null | head -n 20

Git activity (last 10 commits, current branch)

git log --oneline --decorate -n 10 2>/dev/null || echo "(not a git repo)"

Open ports / running listeners (TCP, IPv4)

{ ss -tln 2>/dev/null || netstat -tln 2>/dev/null || lsof -iTCP -sTCP:LISTEN -n 2>/dev/null; } | head -n 30

Resource snapshot

Free memory: !free -h 2>/dev/null | head -n 2 || echo "(free unavailable)"
Load average: !cat /proc/loadavg 2>/dev/null || uptime | sed 's/.*load average: //'
Open file limit: !ulimit -n

Selected env vars

env | grep -E '^(PATH|PYTHONPATH|NODE_ENV|VIRTUAL_ENV|HOME|USER|LANG|TZ|GENY_|ANTHROPIC_|OPENAI_)' | sed 's/=\(sk-\|ghp_\|gho_\)[A-Za-z0-9_-]*/=<redacted>/'

How to interpret

The data above is the input — your job is the output:

Spot the anomaly. What's different from a clean dev box? Stale lock file? Stuck process on an unexpected port? cwd not writable? Dirty worktree masking a real fix?
Tie it to the user's reported symptom. If they said "build fails", point at the disk-full / inode-exhausted / permission mismatch. If they said "tests hang", point at the listener / load / process state.
Recommend at most one or two surgical fixes. Don't shotgun. Diagnostic skills earn trust by being precise.

Read the full file on GitHub · 82 lines

Changes

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.

1mo ago First seen · 82 lines · 34 tokens per session scan A c907a10c41b9

Subscribe to this mod's changes

Debug Snapshot is a skill published in the GitHub repository CocoRoF/geny-executor (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 34 tokens to every session and 835 once invoked, about $0.0001 per session on Opus 5.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-31.

Debugging agent-framework agent-pipeline agentic-ai ai-agents anthropic claude diagnostic

continuum-observability

Trace agent runs with Langfuse, decorate functions with @observe, collect latency/token/error metrics, and report errors. Invoke when the user asks about "see what the LLM was prompted with", "Langfuse traces", "track latency", "metrics dashboard", "error reporting", or "instrument my function".

shyftlabs/continuum · 70 tokens

Debug Snapshot