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 WingedGuardian/GENesis-AGI --skill debugginggit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/wingedguardian/genesis-agi/debugging)<a href="https://agentmods.dev/skills/wingedguardian/genesis-agi/debugging"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/debugging.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.00032 | $0.00596 |
| Opus 5 | $0.00016 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
debugging 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 7d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging
Purpose
Systematically diagnose and resolve bugs, failures, or unexpected behavior in Genesis or its dependencies.
When to Use
- A test fails unexpectedly.
- Runtime error or unexpected behavior is reported.
- An awareness tick or reflection produces anomalous results.
- Obstacle resolution escalates a technical issue.
Workflow
- Reproduce — Confirm the issue. Get the exact error, stack trace, or unexpected output. Define "expected vs. actual."
- Isolate — Narrow the scope. Which module? Which function? Which input triggers it? Use binary search on the call chain.
- Hypothesize — Form 2-3 candidate explanations. Rank by likelihood.
- Test hypotheses — Write a minimal test or add logging to confirm/deny each hypothesis. Start with the most likely.
- Fix — Apply the minimal correct fix. Do not fix adjacent issues in the same change.
- Verify — Run the failing test. Run the full test suite. Confirm no regressions.
- Document — Record the root cause and fix as an observation. Update procedures if the bug class is recurring.
Output Format
issue: <one-line description>
date: <YYYY-MM-DD>
root_cause: <what actually went wrong>
fix: <what was changed>
files_modified:
- <file path>
regression_risk: low | medium | high
lesson: <what to remember to prevent recurrence>
Examples
Example: Hook fails in non-login shell
Trigger: Post-commit hook throws KeyError: 'HOME' in CI-like environment.
Expected output:
issue: Post-commit hook crashes when HOME not set in non-login sessions
date: 2026-04-06
root_cause: Hook script reads os.environ["HOME"] but non-login shells
(systemd, cron) strip HOME from environment
fix: Guard with os.environ.get("HOME", "/root") fallback + persist HOME
in /etc/environment during install
files_modified:
- .claude/hooks/genesis-hook
- scripts/install_guardian.sh
regression_risk: low
lesson: Never assume HOME exists — non-login shells strip it. Always
use get() with fallback for environment variables in hook scripts.
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.
- 7d ago First seen · 79 lines · 32 tokens per session scan A 7cb13a286ee1
debugging is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (95 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 596 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
langfuse
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production.
distributed-tracing
Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
incident-responder
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
arch-debt
Identify architectural anti-patterns — coupling, circular dependencies, God objects — and propose concrete migration paths.
chaos-fault-injection
Deliberately inject faults — dropped connections, corrupted writes, latency, malformed responses, resource exhaustion — and assert the system's expected recovery (escalation, hardstop, rollback).
debug
Systematic root-cause debugging — reproduce, isolate, hypothesize, fix with TDD.