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 Nodewarrior/spine --skill spine-initgit clone --depth 1 https://github.com/Nodewarrior/spineWrote 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/nodewarrior/spine/spine-init)<a href="https://agentmods.dev/skills/nodewarrior/spine/spine-init"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-init.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 28 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00033 | $0.01975 |
| Opus 5 | $0.00016 | $0.00988 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
spine-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 8d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spine Init — Vault Setup Wizard
Initialize a new Spine Architecture vault, or adopt an existing Obsidian vault into the Spine conventions.
Vault Path Resolution
Spine uses a config chain to find the vault:
$SPINE_VAULT_PATHenvironment variable~/.spine/config.json→{ "vaultPath": "..." }- Default:
~/Documents/SpineVault/
Step 1: Determine Mode
If $ARGUMENTS is provided, use it as the vault path. Otherwise, check the config chain for an existing path. If none found, ask the user.
Check if the path already contains an Obsidian vault (.obsidian/ directory) or markdown files:
- If yes → Adopt mode
- If no → Fresh vault mode
Step 2a: Fresh Vault Mode
- Create the vault root directory at the chosen path
- Ask the user: "Enable Tier 3 autonomous mode?"
Explain briefly: "Tier 3 adds session-start scanning, silent commit tracking, and batch capture at session end. You can change this anytime in
~/.spine/config.json."- If yes →
tier3: true - If no (default) →
tier3: false
- If yes →
- Create
~/.spine/config.json:{ "vaultPath": "/absolute/path/to/vault", "tier3": false } - Create
.obsidian/graph.jsonwith color groups:{ "collapse-filter": true, "search": "", "showTags": false, "showAttachments": false, "hideUnresolved": false, "showOrphans": true, "collapse-color-groups": false, "colorGroups": [ { "query": "tag:#type/spine", "color": { "a": 1, "rgb": 3381759 } }, { "query": "tag:#type/fix", "color": { "a": 1, "rgb": 14495282 } }, { "query": "tag:#type/feature", "color": { "a": 1, "rgb": 4439473 } }, { "query": "tag:#type/architecture", "color": { "a": 1, "rgb": 10170623 } }, { "query": "tag:#type/plan", "color": { "a": 1, "rgb": 16750848 } }, { "query": "tag:#type/decision", "color": { "a": 1, "rgb": 16776960 } }, { "query": "tag:#type/meta", "color": { "a": 1, "rgb": 10066329 } } ], "collapse-display": true, "showArrow": false, "textFadeMultiplier": 0, "nodeSizeMultiplier": 1, "lineSizeMultiplier": 1, "collapse-forces": true, "centerStrength": 0.5, "repelStrength": 10, "linkStrength": 1, "linkDistance": 250, "scale": 1.6, "close": true } - Write
Spine Architecture.mdat the vault root:
{vault}/ └─ {repo}/ └─ {feature}/ ├─ {Feature}.md ← spine note (overview, wikilinks to all children) ├─ Fix - {description}.md ├─ Feature - {description}.md ├─ Architecture - {description}.md ├─ Plan - {description}.md └─ Decision - {description}.md--- tags: - type/meta --- # Spine Architecture A knowledge management system that bridges Claude Code's memory with this Obsidian vault, organizing project knowledge as a navigable graph tree. ## Structure## Navigation Claude Memory → Feature Signpost → Spine Note → Specific Doc ## Conventions - **Repo-first** hierarchy separates concerns across codebases - **Feature-first** grouping within each repo keeps related knowledge together - **Spine notes** are the entry point — read the spine to understand a feature before diving in - **Naming convention** (`Fix -`, `Feature -`, `Architecture -`, `Plan -`, `Decision -`) keeps the tree shallow - **Type tags** (`type/spine`, `type/fix`, `type/feature`, `type/architecture`, `type/plan`, `type/decision`) drive graph coloring - **Cross-repo features** link to each other via `[[wikilinks]]` - Detect the current repo name from
basename $(git remote get-url origin 2>/dev/null) .gitor the current directory name - Create the first repo folder:
{vault}/{repo}/ - Ask the user: "What's the first feature you'd like to track?"
- Create the feature folder and spine note using the template:
--- title: {Feature} — {repo} tags: - {repo} - {feature-kebab-case} - type/spine --- # {Feature} ({repo}) {Brief description — ask user or derive from context} ## Fixes ## Features ## Architecture ## Plans ## Decisions
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.
- 8d ago First seen · 205 lines · 33 tokens per session scan A acb63a3f6f4f
spine-init is a skill published in the GitHub repository Nodewarrior/spine (22 stars, last pushed 13d ago), licensed MIT. It adds 33 tokens to every session and 1,975 once invoked, about $0.0002 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.