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/commands/giggsoinc/raven/raven-registry-register)<a href="https://agentmods.dev/commands/giggsoinc/raven/raven-registry-register"><img src="https://agentmods.dev/badge/commands/giggsoinc/raven/raven-registry-register/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/commands/giggsoinc/raven/raven-registry-register"><img src="https://agentmods.dev/badge/commands/giggsoinc/raven/raven-registry-register.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.00051 | $0.00916 |
| Opus 5 | $0.00026 | $0.00458 |
| Sonnet 5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
raven-registry-register 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 10d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/raven-registry-register
Registers a project in the Raven registry (~/.raven/registry.json), enabling
/raven-registry-sync to keep it updated automatically.
Registry: ~/.raven/registry.json (backed up to giggsoinc/raven-registry)
Usage
/raven-registry-register → register current directory
/raven-registry-register --path /abs/path → register a specific project
/raven-registry-register --list → list all registered projects
/raven-registry-register --remove NAME → remove a project from registry
Steps — Register
-
Locate raven-core
RAVEN_CORE=~/projects/raven-core REGISTER_SCRIPT="$RAVEN_CORE/registry/raven-register.py"If not found → STOP with: "raven-core not found. Check ~/projects/raven-core"
-
Determine target path
- If
--pathwas provided → use that path - Otherwise → use the project's working directory (where Claude is operating)
- If
-
Run registration:
python3 "$REGISTER_SCRIPT" --path "$TARGET_PATH" -
Show result — expected output:
✅ Registered: my-service path: /Users/you/projects/my-service remote: https://github.com/yourorg/my-service.git version: unknown (no .raven/raven_version found — run /raven-registry-sync) scripts: ✅ mcp: ✅ skills: raven-core, raven-security, andie -
After registering, suggest running
/raven-registry-sync --project NAMEto immediately stamp the project with the current version.
Steps — List
python3 "$REGISTER_SCRIPT" --list
Output shows all registered projects with installed vs current version and sync status:
Raven Registry — 3 project(s) [current: v2.8.0]
Name Installed Status Remote
────────────────────────────────────────────────────────────────────────────
my-project 2.8.0 ✅ current https://github.com/...
my-service unknown ⚠️ stale (unknown→2.8.0) local only
Dev-Claude-Arch 2.7.0 ⚠️ stale (2.7.0→2.8.0) local only
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.
- 10d ago First seen · 129 lines · 51 tokens per session scan A 69b238b317dd
raven-registry-register is a command published in the GitHub repository giggsoinc/raven (5 stars, last pushed 10d ago), licensed MIT. It adds 51 tokens to every session and 916 once invoked, about $0.0003 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-31.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.