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/skills/giggsoinc/raven/raven-init)<a href="https://agentmods.dev/skills/giggsoinc/raven/raven-init"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/raven-init/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-init"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/raven-init.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.00041 | $0.01770 |
| Opus 5.5 | $0.00016 | $0.00708 |
| Sonnet 5.5 | $0.00008 | $0.00354 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
raven-init 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/raven init — Andie-Conversational Setup
Replaces the legacy 7-step interactive wizard with an Andie-driven conversation. Auto-detects everything possible, asks only what cannot be inferred.
Entry Points
This skill is invoked by:
- Andie Branch A onboarding — fires automatically when no manifest exists and user confirms "OK to proceed".
- Explicit
/raven init— user runs the command directly. andie init— user invokes Andie for setup.
Pre-checks
-
Is
.raven/manifest.jsonalready present?- YES → Load it. Trust it. Proceed with the declared stack. Do not reinitialize. Do not modify unless user explicitly requests it.
- NO → Run the auto-scan flow below.
-
Is Git initialized?
- NO → Note silently: "Git not initialized — audit trail will start when you
git init." Continue.
- NO → Note silently: "Git not initialized — audit trail will start when you
Auto-Scan (Silent, Fast)
Scan the project root for these signals. No prompts. No noise. Just detect.
| Signal File | Infers |
|---|---|
package.json |
Node/JS · framework from deps (React/Vue/Next/etc.) · scripts |
pyproject.toml / requirements.txt / setup.py |
Python · libraries · framework (FastAPI/Django/Flask) |
Cargo.toml |
Rust |
go.mod |
Go |
pom.xml / build.gradle |
Java/Kotlin |
Gemfile |
Ruby |
sfdx-project.json / force-app/ |
Salesforce |
__manifest__.py |
Odoo |
*.tf files |
Terraform |
Dockerfile / docker-compose.yml |
Container stack |
helm/ / charts/ / k8s/ |
Kubernetes |
.env* / secrets.json |
Mark as sensitive — do NOT read |
git remote -v |
Owner (from GitHub URL) |
.git/config |
Branch info |
Output silently to working memory — NOT to the user.
Inference Rules
From the scan, infer the manifest defaults:
| Manifest field | Inference source |
|---|---|
project |
Folder name |
owner |
git remote URL (giggsoinc/foo → "giggsoinc") |
stack.language |
From signal files above |
stack.frontend |
From package.json frameworks |
stack.db |
From requirements (psycopg2 → postgres, etc.) |
stack.infra |
From .tf, Dockerfile, k8s/ presence |
stack.cloud |
"on-prem" default, override if AWS/Azure/GCP detected |
stack.libraries |
From requirements/package.json |
standards |
"raven-v1" default |
approval_mode |
"first_responder" default |
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 · 202 lines · 41 tokens per session scan A bf084058ebf8
raven-init is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 13d ago), licensed MIT. It adds 41 tokens to every session and 1,770 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.
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,"…