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 giggsoinc/raven --skill raven-registry-syncgit 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/skills/giggsoinc/raven/raven-registry-sync)<a href="https://agentmods.dev/skills/giggsoinc/raven/raven-registry-sync"><img src="https://agentmods.dev/badge/skills/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/skills/giggsoinc/raven/raven-registry-sync"><img src="https://agentmods.dev/badge/skills/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.00981 |
| Opus 5.5 | $0.00031 | $0.00392 |
| Sonnet 5.5 | $0.00016 | $0.00196 |
| Haiku 4.5 | $0.00008 | $0.00098 |
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 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.
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 — 124 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 (checked in order — first hit wins)
for candidate in "${RAVEN_CORE_PATH:-}" "./raven-core" "$(pwd)/raven-core" ~/projects/raven-core; do if [ -n "$candidate" ] && [ -f "$candidate/registry/raven-sync.py" ]; then RAVEN_CORE="$candidate" break fi done SYNC_SCRIPT="$RAVEN_CORE/registry/raven-sync.py"Set
RAVEN_CORE_PATHenv var to override on unusual layouts. If none found → STOP with: "raven-core not found — checked $RAVEN_CORE_PATH, ./raven-core, ~/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.
- 1mo ago First seen · 124 lines · 78 tokens per session scan A 632157247ef8
raven-registry-sync is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 13d ago), licensed MIT. It adds 78 tokens to every session and 981 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…