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-healthgit 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-health)<a href="https://agentmods.dev/skills/nodewarrior/spine/spine-health"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-health/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/nodewarrior/spine/spine-health"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.01384 |
| Opus 5 | $0.00015 | $0.00692 |
| Sonnet 5 | $0.00006 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
spine-health 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 12d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spine Health — Vault Curator Scan
Audit the Spine Architecture vault for quality and completeness.
Vault Path Resolution
Resolve the vault path using this config chain:
$SPINE_VAULT_PATHenvironment variable~/.spine/config.json→ read thevaultPathfield- Default:
~/Documents/SpineVault/
If the vault doesn't exist, tell the user to run /spine-init first.
Scope
If $ARGUMENTS specifies a feature or repo, limit the scan to that area. Otherwise, scan the entire vault.
Check 1: Coverage Gaps
Compare recent git history against existing Obsidian docs to find undocumented work.
- Run
git log --oneline --since="2 weeks ago"in the current repo - Group commits by feature area (based on file paths changed)
- For each group, check if a corresponding Obsidian doc exists
- Report any significant work (not just typo fixes) that has no documentation
Output:
## Coverage Gaps
- [repo/feature] 3 commits touching auth logic — no doc since YYYY-MM-DD
- [repo/feature] New API endpoint added — no architecture doc
Check 2: Stale Docs
Find docs that reference code that has changed significantly since the doc was written.
- Read each doc's
**Files changed:**section - For each referenced file, check
git log --oneline --since="{doc date}" -- {filepath} - If the file has 3+ commits since the doc was written, flag as potentially stale
Output:
## Potentially Stale
- Fix - Session Bug (2026-03-18) — session.hook.ts has 5 commits since
Check 3: Duplicate/Overlapping Docs
Find docs within the same feature that describe overlapping issues.
- Read all docs under each feature folder
- Check for:
- Same files referenced in multiple docs
- Similar root causes described
- Wikilinks that create circular clusters
- Suggest consolidation where appropriate
Check 4: Spine Note Integrity
Verify each spine note accurately reflects its children.
- List all files in each feature folder
- Compare against wikilinks in the spine note
- Flag:
- Docs that exist but aren't linked from the spine
- Wikilinks that point to non-existent docs (ghost links)
- Missing sections (e.g., feature has fixes but spine has no "## Fixes" section)
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.
- 12d ago First seen · 148 lines · 31 tokens per session scan A 10d4c6b5bbe1
spine-health is a skill published in the GitHub repository Nodewarrior/spine (22 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 1,384 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.