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.
npx skills add ivanhoinacki/team-exp-claude-config --skill debug-modegit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/skills/ivanhoinacki/team-exp-claude-config/debug-mode)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/debug-mode"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/debug-mode.svg" alt="Measured on agentmods" 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.00120 | $0.03133 |
| Opus 5 | $0.00060 | $0.01566 |
| Sonnet 5 | $0.00024 | $0.00627 |
| Haiku 4.5 | $0.00012 | $0.00313 |
Grade B, and why
debug-mode scanned grade B with 2 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 8d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
void fetch("http://127.0.0.1:7777", { method: "POST", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Requires node, lsof, curl, git, gh (GitHub CLI) How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Vault RAG (MANDATORY, BEFORE any Read/Grep)
You MUST call query_vault(query, service_filter) BEFORE reading codebase files or external sources. This is enforced by hook. No exceptions.
Debug Mode
Working Directories
Always consider these directories as primary sources when investigating bugs:
- Obsidian workspace (docs, plans, features):
__VAULT_ROOT__ - Codebase (all LE services):
__CODEBASE_ROOT__
You are now in Debug Mode. Follow a strict hypothesis-driven workflow. Do NOT guess fixes from static analysis alone.
Common Agent Mistakes
- Guessing from static analysis: Making code changes based on reading code alone without gathering runtime evidence (logs, traces, metrics). The whole point of debug-mode is evidence-based debugging.
- Fixing symptoms, not causes: Patching the error handler or adding a null check without understanding WHY the value is null. Always trace back to the root cause.
- Not reproducing first: Attempting to fix a bug without confirming it exists in the expected environment. Check: does the bug happen in staging? prod? local?
- Ignoring the service chain: The bug may originate in an upstream service. Check the Experiences Ecosystem doc for the data flow chain before diving into one service.
- Skipping hypothesis documentation: Making changes without writing down the hypothesis first. Each fix attempt should be: hypothesis -> evidence -> change -> verify.
- Not checking recent deploys: A bug may have been introduced by a recent deployment. Always check
git log --oneline -10and recent CircleCI deploys before deep diving. - Not checking KB before attempting fix: When encountering an error, immediately trying to fix it without running
query_vault+grep pitfalls*.mdfirst. The KB has documented fixes for dozens of known errors. A 2-second vault check prevents a 10-minute retry loop. ALWAYS check vault BEFORE your first fix attempt.
References
- Evidence Collection Patterns - Datadog/NR queries, browser console, codebase evidence
- Debug Mode Learnings - Lessons from past debugging sessions
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 267 lines · 120 tokens per session scan B ad4c4cdb09a0
debug-mode is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 3,133 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…