Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add giggsoinc/raven/plugin install ravenWrote 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/giggsoinc/raven/raven-debug)<a href="https://agentmods.dev/skills/giggsoinc/raven/raven-debug"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/raven-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/skills/giggsoinc/raven/raven-debug"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/raven-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.00041 | $0.01235 |
| Opus 5.5 | $0.00016 | $0.00494 |
| Sonnet 5.5 | $0.00008 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade B, and why
raven-debug 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
13. **manifest.secrets.json permissions** — warn if not chmod 600 How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/raven-debug
First: Check If Raven Is Initialized
Before running any diagnostics:
Is .raven/manifest.json present?
NO MANIFEST — First-Run Discovery
If .raven/manifest.json does NOT exist:
Do NOT error. Do NOT say "manifest missing — hard stop."
Instead, say this:
─────────────────────────────────────────────────
RAVEN — not set up yet for this project
─────────────────────────────────────────────────
No manifest found at .raven/manifest.json
Raven can help with this project. Here's what
I can see in the current directory:
[Run: python3 .claude/scripts/sr-detect-workmode.py .]
[Display the signals and detected mode from the output]
This looks like a [detected mode] project.
Want me to set Raven up now?
1) Yes — set it up (takes 2 minutes)
2) No — just tell me what Raven would do here
3) Show me the manifest that would be created
→
If user says 1: Run the setup flow inline (ask the 2-3 questions, create the manifest, confirm). If user says 2: Describe what Raven would enforce for the detected mode, no manifest created. If user says 3: Generate and display the manifest JSON without saving it. Ask "Save this? [y/n]".
This is the correct behaviour when a developer runs raven-debug as their first command — they're exploring. Reward that, don't punish it.
MANIFEST EXISTS — Full Diagnostic
First (mandatory, public path): engine into app repo + dashboard — do not skip:
python3 scripts/ops/raven-first.py --boot
Fallback if the app repo has no scripts/ops/raven-first.py yet:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/ops/raven-first.py" --boot
(RAVEN_PLUGIN_ROOT also works.) This copies scripts/raven-python.sh, scripts/routing|memory|session|ops, .agents/agents.md / AGENTS.md, and runs ide-boot. Then run checks in order. Output ✅ or ❌ per check.
0-HARD — model-router (primary Codex / public-plugin gate): After raven-first, scripts/routing/model-router.py MUST exist in the project or under CLAUDE_PLUGIN_ROOT / RAVEN_PLUGIN_ROOT. If both are missing → FAIL immediately. Do not treat Claude Notification hook registration as the primary Codex error — empty/missing router is the defect.
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 · 130 lines · 41 tokens per session scan B 1df06918314f
raven-debug is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 13d ago), licensed MIT. It adds 41 tokens to every session and 1,235 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
ci-fixer
CI failures - read error, minimal fix, verify.
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…