raven-registry-register

raven-registry-register is a skill for Claude Code from giggsoinc/raven. It costs 51 tokens per session (916 once invoked), scanned A, original, MIT.

A registration tool that adds a project to Raven’s central list of projects.

In plain words
What is it for?
Use it to register the current project or a specified path, list registered projects, or remove stale entries.
Why use it?
It ensures the project can be included in future Raven-wide update runs.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/you/projects/my-service.

Part of the raven plugin — 63 skills, 13 commands, 10 agents, 5 hooks, 1 MCP server shipped together

Good fit Use it to register the current project or a specified path, list registered projects, or remove stale entries.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add giggsoinc/raven
Claude Code
/plugin install raven

Made for: Claude Code.

Or install raven, the plugin that ships this one along with the rest of its 63 skills, 13 commands, 10 agents, 5 hooks, 1 MCP server.

Wrote 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.

agentmods badge for raven-registry-register

README.md
[![agentmods](https://agentmods.dev/badge/skills/giggsoinc/raven/raven-registry-register/github.svg)](https://agentmods.dev/skills/giggsoinc/raven/raven-registry-register)
Your own site
<a href="https://agentmods.dev/skills/giggsoinc/raven/raven-registry-register"><img src="https://agentmods.dev/badge/skills/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.

agentmods 80×15 button for raven-registry-register

Your own site · 80×15
<a href="https://agentmods.dev/skills/giggsoinc/raven/raven-registry-register"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/raven-registry-register.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 916 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00916
Opus 5.5 $0.00020 $0.00366
Sonnet 5.5 $0.00010 $0.00183
Haiku 4.5 $0.00005 $0.00092

Measured 1mo ago against content hash 69b238b317dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/raven-registry-register/SKILL.md · 129 lines

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

  1. 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"

  2. Determine target path

    • If --path was provided → use that path
    • Otherwise → use the project's working directory (where Claude is operating)
  3. Run registration:

    python3 "$REGISTER_SCRIPT" --path "$TARGET_PATH"
    
  4. 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
    
  5. After registering, suggest running /raven-registry-sync --project NAME to 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

Read the full file on GitHub · 129 lines

Changes

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.

  1. 1mo ago First seen · 129 lines · 51 tokens per session scan A 69b238b317dd

Subscribe to this mod's changes

raven-registry-register is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 13d ago), licensed MIT. It adds 51 tokens to every session and 916 once invoked, about $0.0002 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.

Related

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.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

specstoryai/getspecstory · 126 tokens

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…

LerianStudio/ring · 104 tokens

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,"…

petrkindlmann/qa-skills · 124 tokens