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-capturegit 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-capture)<a href="https://agentmods.dev/skills/nodewarrior/spine/spine-capture"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-capture/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-capture"><img src="https://agentmods.dev/badge/skills/nodewarrior/spine/spine-capture.svg" alt="Reviewed on agentmods" width="80" 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 155 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.00054 | $0.02536 |
| Opus 5 | $0.00027 | $0.01268 |
| Sonnet 5 | $0.00011 | $0.00507 |
| Haiku 4.5 | $0.00005 | $0.00254 |
Grade A, and why
spine-capture 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 9d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spine Capture — Document Work to Obsidian Vault
Capture completed work into the Spine Architecture vault.
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.
Doc Types and Prefixes
| Prefix | Tag | When to use |
|---|---|---|
Fix - {description} |
type/fix |
Bug fix — include root cause and code snippets |
Feature - {description} |
type/feature |
New functionality |
Architecture - {description} |
type/architecture |
Design doc, API structure, data flow |
Plan - {description} |
type/plan |
Implementation plan |
Decision - {description} |
type/decision |
Decision record with context and trade-offs |
Date prefixes: Add YYYY-MM-DD prefix on Fix and Feature docs only. No date prefix on Architecture, Plan, or Decision docs.
Step 1: Determine What to Capture
If $ARGUMENTS is provided, use that as the description. Otherwise:
- Run
git log --oneline -10andgit diff main...HEAD --statto see recent work - Read any recently modified source files to understand the change
- Ask the user: "What type of doc is this?" (fix / feature / architecture / plan / decision) — unless obvious from context
Step 2: Determine Repo and Feature
-
Repo: Detect from the git remote:
basename "$(git remote get-url origin 2>/dev/null)" .gitFall back to the current directory name if no git remote.
-
Feature: Read existing spine notes at
{vault}/{repo}/to find matching features. Match by:- File paths changed (which feature folder do they map to?)
- Component names, module names
- If no match, ask the user: "This looks like a new feature area. What should I call it?"
- For new features, create the folder and spine note
Step 3: Draft the Obsidian Doc
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.
- 9d ago First seen · 251 lines · 54 tokens per session scan A 6dd64ada353a
spine-capture is a skill published in the GitHub repository Nodewarrior/spine (22 stars, last pushed 15d ago), licensed MIT. It adds 54 tokens to every session and 2,536 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…