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 agentmods add commands/giggsoinc/raven/raven-debuggit clone --depth 1 https://github.com/giggsoinc/ravenWhat 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 | $0.00041 | $0.00916 |
| Opus 5 | $0.00020 | $0.00458 |
| Sonnet 5 | $0.00008 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 3d 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 — 110 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
Run these checks in order. Output ✅ or ❌ per check.
- CLAUDE.md — exists at project root?
- manifest.json — valid JSON, all required fields present?
- manifest.json → stack.work_type — present and valid? (code/infra/data/docs/review/mixed/salesforce/odoo)
- manifest.secrets.json — present? (warn if missing, not hard stop)
- .gitignore — exists at project root?
- .gitignore entries — covers
.env,*.pem,*.key,manifest.secrets.json? - .env files — present but gitignored? (warn if exposed)
- .claude/agents/ — list all loaded agents (count + names)
- .claude/skills/ — list all loaded skills (count + names)
- .claude/settings.json — hooks registered (PreToolUse, PostToolUse, PreCompact, Notification)?
- .git/hooks/pre-commit — executable?
- .raven/architecture.md — exists? (warn if missing — not a hard stop)
- manifest.secrets.json permissions — warn if not chmod 600
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.
- 3d ago First seen · 110 lines · 41 tokens per session scan B d202e4b1acf3
raven-debug is a command published in the GitHub repository giggsoinc/raven (5 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 916 once invoked, about $0.0002 per session on Opus 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-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.