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 RaNDoM6913/claude-code-superkit --skill debug-observergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/debug-observer)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/debug-observer"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/debug-observer/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/skills/random6913/claude-code-superkit/debug-observer"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/debug-observer.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.00043 | $0.02372 |
| Opus 5.5 | $0.00017 | $0.00949 |
| Sonnet 5.5 | $0.00009 | $0.00474 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade B, and why
debug-observer scanned grade B with 1 finding 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 today.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Check runtime semantics before interpreting TTL results (for Redis, no-expiry and missing-key states differ). Missing cache/session data may reflect expiry, eviction, a different namespace, or observation timing, not nec How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Observer
Build an evidence-backed explanation of a reported symptom. Correlate relevant sources rather than collecting everything: service/process state, logs, database/cache state, code paths, version history, and actual deployment records. A useful result may be a narrowed hypothesis and one discriminating next check; do not force a root cause when evidence is insufficient.
Input, scope, and authority
Use the supplied symptom, endpoint, error message, correlation/entity identifier, and incident time window. Establish the affected service/environment, expected versus observed behavior, relevant version, and what access is already authorized. If a required target or time window is ambiguous, resolve it before querying sensitive/live systems; continue bounded local source inspection where useful.
Read applicable AGENTS.md first, then relevant architecture, runbooks, manifests, and configuration structure. Use compose files/imports/manifests to identify candidate services and stack versions, not to assert they are running. Prefer configuration names or redacted templates. When diagnosis already authorizes checking a specifically identified non-secret setting available only in .env or another local config, inspect that setting through local selection and filtering/redaction before any model-visible output. Establish its non-secret meaning from the actual schema, code, or documented contract; a key name alone does not establish that its value is safe. Never dump raw config, discover credentials, expose secret values or credential-bearing URLs, or source/evaluate configuration as executable code. If safe filtering or task authority is unavailable, report the bounded evidence gap. Do not request renewed approval for an already-authorized safe check; local configuration access does not itself authorize external access.
Observe only. Use existing approved read-only connection methods and least-privilege access for the assigned environment. Do not expose secrets in shell arguments, URLs, prompts, logs, or reports; do not run full environment dumps, connection-string prints, or process listings that reveal credential-bearing arguments. A tool being installed or credentials being reachable does not grant authority. If approved access is absent, mark that source unavailable and provide the exact safe evidence needed.
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.
- today Changed · -42 lines · +21 tokens per session scan A → B 3bf8ea7d8521
- 1mo ago First seen · 150 lines · 22 tokens per session scan A f7ca542d4e67
debug-observer is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 2,372 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
Diagnose
When something feels off, type /diagnose and describe the symptom. The skill walks the seven-layer stack (kernel, skills, hooks, daemons, vault, doctrine, principal config) and reports which layer is most likely responsible. Caddy pattern applied to debugging.
First 10 Moves
The exact operational recon sequence for an unfamiliar codebase or unfamiliar area. Replaces "ask the human to clarify" with "read the code first." Most clarification questions are answered by 5 minutes in the relevant file - this skill enforces reading before asking.
Stuck
Walk the 6-rung escalation ladder before declaring stuck or asking the principal. Most "stuck" is actually "haven't tried the next approach." Stopping is the last resort, not the first response.
learn-from-failure
When a failure occurs, classify it, check for repetition, and produce a durable artifact that prevents recurrence.
solution-hunt
When blocked, systematically search for legitimate alternate routes before declaring inability.
system-check
Read-only installation smoke test for skills, daemons, operational memory, cognitive runtime, nightly freshness, terminal evidence, and unique route ownership.