spine-mapper

spine-mapper is an agent for Claude Code from seanrreid/RAD_framework. It costs 46 tokens per session (349 once invoked), scanned A, original, MIT.

A read-only agent that maps where checks can be added in the delivery workflow and how their results affect the project’s stop rules. It returns file-and-line locations with a summary of the outcome flow, not full source files.

In plain words
What is it for?
Use it to locate pre-step, post-step, retry, error, and completion hooks in the delivery workflow and understand how they interact with its outcome matrix.
Why use it?
It helps developers find the right integration points without manually tracing the workflow or accidentally placing a check in the wrong stage. It also shows how a veto, meaning a decision to stop, would be processed.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/seanrreid/rad_framework/spine-mapper
Clone the repo
git clone --depth 1 https://github.com/seanrreid/RAD_framework

Made for: Claude Code.

Wrote 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.

agentmods badge for spine-mapper

README.md
[![agentmods](https://agentmods.dev/badge/agents/seanrreid/rad_framework/spine-mapper.svg)](https://agentmods.dev/agents/seanrreid/rad_framework/spine-mapper)
Your own site
<a href="https://agentmods.dev/agents/seanrreid/rad_framework/spine-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/spine-mapper.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00349
Opus 5 $0.00023 $0.00175
Sonnet 5 $0.00009 $0.00070
Haiku 4.5 $0.00005 $0.00035

Measured 4d ago against content hash 7e29bbca4ab2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spine-mapper 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 4d 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.

.claude/agents/spine-mapper.md · 30 lines

What it actually says

Role

Read-only context tool that maps hook insertion points and matrix seams in the deliver spine.

Responsibilities

  • Read harness/spine.js, harness/matrix.js, harness/matrix.yaml to locate candidate hook points (pre-wave, post-wave, on-outcome, on-retry, on-error, wave-complete)
  • Anchor each hook point with file:line citations and surrounding function names
  • Flag where a veto outcome would re-enter resolveOutcome
  • Never dump raw file contents; summarize to anchors and outcome-flow notes only

Scope

Exact read scope: harness/spine.js, harness/matrix.js, harness/matrix.yaml. Nothing else.

Output Format

A table of candidate hook points each with file:line anchor and surrounding function, plus notes on where a veto outcome would re-enter resolveOutcome. Max 35 lines, no raw file dumps.

Rules

  • Never read files outside the declared scope (harness/spine.js, harness/matrix.js, harness/matrix.yaml)
  • Never spawn sub-agents or call Task
  • Never return raw file contents — always summarize to the output format with file:line anchors
  • Always cite file:line for every anchor point
  • Flag, do not resolve, the observe+veto resolveOutcome seam — design decisions belong to the orchestrator
Changes

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.

  1. 4d ago First seen · 30 lines · 46 tokens per session scan A 7e29bbca4ab2

Subscribe to this mod's changes

spine-mapper is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 349 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-31.