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.
git clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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.
[](https://agentmods.dev/commands/versoxbt/claude-initial-setup/debug)<a href="https://agentmods.dev/commands/versoxbt/claude-initial-setup/debug"><img src="https://agentmods.dev/badge/commands/versoxbt/claude-initial-setup/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.
<a href="https://agentmods.dev/commands/versoxbt/claude-initial-setup/debug"><img src="https://agentmods.dev/badge/commands/versoxbt/claude-initial-setup/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00009 | $0.00511 |
| Opus 5.5 | $0.00004 | $0.00204 |
| Sonnet 5.5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
debug 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic Debugging
Follow a structured approach to identify, isolate, and fix bugs efficiently.
Steps
-
Reproduce the issue:
- Identify the exact steps, inputs, or conditions that trigger the bug.
- Confirm the issue is reproducible and not intermittent.
- Note the expected behavior versus the actual behavior.
-
Gather evidence:
- Read error messages, stack traces, and log output carefully.
- Check recent changes to see if the bug was introduced recently.
- Identify the affected files and functions from the stack trace.
git log --oneline -20 git diff -
Form a hypothesis:
- Based on the evidence, propose what is causing the bug.
- Write down the hypothesis before investigating further.
-
Isolate the root cause:
- Use binary search / bisect to narrow down the problem area.
- If recent regression: use
git bisectto find the offending commit. - If logic error: add targeted logging or use a debugger to trace execution flow.
- Verify assumptions — check that inputs, state, and dependencies are what you expect.
git bisect start git bisect bad HEAD git bisect good <known-good-commit> -
Validate the hypothesis:
- Confirm the root cause matches the observed behavior.
- If the hypothesis is wrong, return to step 3 with new evidence.
-
Implement the fix:
- Fix the root cause, not just the symptom.
- Use immutable patterns — do not mutate existing objects.
- Keep the fix minimal and focused.
-
Verify the fix:
- Reproduce the original steps — the bug should no longer occur.
- Run the full test suite to check for regressions.
- Write a test that would have caught this bug to prevent recurrence.
-
Check for related issues:
- Search the codebase for similar patterns that may have the same bug.
- Fix any related occurrences found.
If the Bug Cannot Be Reproduced
- Check environment differences (OS, Node version, database state).
- Review logs from the environment where the bug occurred.
- Add additional logging to capture more context for next occurrence.
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 · 69 lines · 9 tokens per session scan A 4f9dd7c1d6b1
debug is a command published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 511 once invoked, about $0.0000 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.
Other commands, from other repositories
unity-ralph
Relentless verify-fix loop — refuses to stop until the project is clean. Runs unity-verifier repeatedly with configurable max iterations and stall detection.
unity-doctor
Diagnostic health check — verifies MCP connectivity, .claude/ integrity, Unity project structure, and hook registration.
unity-audit
Full project health check — meta file integrity, missing references, assembly definition graph, code quality scan, scene hierarchy audit.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.
unity-fix
Diagnoses and fixes a Unity bug — reads console errors, checks common causes, applies targeted fix, verifies via MCP.
story-continue
Resume an interrupted story from where you left off.