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 Nodewarrior/spine/plugin install 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-sessions)<a href="https://agentmods.dev/skills/nodewarrior/spine/spine-sessions"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-sessions/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-sessions"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-sessions.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.00052 | $0.01416 |
| Opus 5 | $0.00026 | $0.00708 |
| Sonnet 5 | $0.00010 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
spine-sessions 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 10d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spine Sessions — Episodic Memory Search
Answer "what did we do / decide / try in a past session?" from two sources:
- Episode log (fast, curated):
{vault}/.spine/episodes/{repo}.md— one record per session (title, date, branch, last prompt, asks, files touched), written by the Stop hook. - Raw transcripts (deep, verbatim):
~/.claude/projects/{escaped-cwd}/*.jsonl— full session history, searched with type-filtered ripgrep.
No LLM calls in the search loop — this skill is deterministic recipes. Speed: full-corpus ripgrep is sub-second; never summarize results with extra model passes unless the user asks.
Vault Path Resolution
Same config chain as all Spine skills:
$SPINE_VAULT_PATHenvironment variable~/.spine/config.json→vaultPathfield- Default:
~/Documents/SpineVault/
Mode Selection (inferred from $ARGUMENTS)
| Arguments | Mode |
|---|---|
| empty | Browse — list recent sessions |
| a UUID-looking token | Read — open that session's episode / transcript |
| anything else | Discover — search episodes, then transcripts |
Mode: Browse
- Resolve repo name:
basename "$(git remote get-url origin 2>/dev/null)" .git(fall back to directory name). - Show the tail of the episode log:
grep -E '^## |^- \*\*session' "{vault}/.spine/episodes/{repo}.md" | tail -20 - If no episode log exists, fall back to transcript listing:
wherels -t ~/.claude/projects/{escaped-cwd}/*.jsonl | head -10{escaped-cwd}is the current working directory with/and.replaced by-(e.g./Users/jane/Git/spine→-Users-jane-Git-spine). - Present: date — title — session id — resume command.
Mode: Discover
Tier 1 — episode log (always first)
grep -n -i -F -B2 -A8 -e "{query}" "{vault}/.spine/episodes/{repo}.md"
Query hygiene (all modes): treat {query} as literal text — use -F and pass it after -e (or --) so queries starting with - or containing regex metacharacters can't be misread as flags or patterns. Drop -F only when the user explicitly gives a regex.
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.
- 10d ago First seen · 118 lines · 52 tokens per session scan A e1d7d9043e04
spine-sessions is a skill published in the GitHub repository Nodewarrior/spine (22 stars, last pushed 15d ago), licensed MIT. It adds 52 tokens to every session and 1,416 once invoked, about $0.0003 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.