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.
git clone --depth 1 https://github.com/giggsoinc/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-sync)<a href="https://agentmods.dev/commands/giggsoinc/raven/raven-registry-sync"><img src="https://agentmods.dev/badge/commands/giggsoinc/raven/raven-registry-sync/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-sync"><img src="https://agentmods.dev/badge/commands/giggsoinc/raven/raven-registry-sync.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.00078 | $0.00884 |
| Opus 5 | $0.00039 | $0.00442 |
| Sonnet 5 | $0.00016 | $0.00177 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
raven-registry-sync 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 9d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/raven-registry-sync
Syncs all registered Raven projects to the current engine version.
Source of truth: raven-core/VERSION
Registry: ~/.raven/registry.json (backed up to giggsoinc/raven-registry)
Usage
/raven-registry-sync → interactive: shows report, asks before updating
/raven-registry-sync --dry-run → report only, no changes made
/raven-registry-sync --all → update all stale projects without prompting
/raven-registry-sync --project NAME → update one specific project
/raven-registry-sync --check → CI mode: exit 1 if any project stale
Steps
-
Locate raven-core
RAVEN_CORE=~/projects/raven-core SYNC_SCRIPT="$RAVEN_CORE/registry/raven-sync.py"If not found → STOP with: "raven-core not found at expected path. Check ~/projects/raven-core"
-
Run the sync script with the flags passed by the user:
python3 "$SYNC_SCRIPT" [FLAGS] -
Show output — the script produces a full report:
──────────────────────────────────────────────────────────── Raven Sync — current version: v2.8.0 ──────────────────────────────────────────────────────────── ✅ Up to date (1) my-project v2.8.0 ⚠️ Stale — needs update (2) my-service v2.7.0 → v2.8.0 Dev-Claude-Arch unknown → v2.8.0 ❌ Path not found (0) -
After sync completes, confirm:
- Which projects were updated
- Which were committed and pushed
- Registry GitHub status
What Gets Updated Per Project
| Component | Destination |
|---|---|
| Engine scripts (4 py files) | .claude/scripts/ |
MCP server (server.py) |
.claude/mcp/ |
| Andie skill | .claude/skills/andie/ |
| Andie Jr skill | .claude/skills/andie-jr/ |
| Tools landscape | .claude/skills/tools-landscape/ |
| Version stamp | .raven/raven_version |
| Git commit | Auto-committed |
| Git push | Auto-pushed (if remote exists) |
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.
- 9d ago First seen · 118 lines · 78 tokens per session scan A de6fdb5a3b7d
raven-registry-sync is a command published in the GitHub repository giggsoinc/raven (5 stars, last pushed 8d ago), licensed MIT. It adds 78 tokens to every session and 884 once invoked, about $0.0004 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.