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 PetriLahdelma/project-spine --skill project-spine-driftgit clone --depth 1 https://github.com/PetriLahdelma/project-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/petrilahdelma/project-spine/project-spine-drift)<a href="https://agentmods.dev/skills/petrilahdelma/project-spine/project-spine-drift"><img src="https://agentmods.dev/badge/skills/petrilahdelma/project-spine/project-spine-drift/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/petrilahdelma/project-spine/project-spine-drift"><img src="https://agentmods.dev/badge/skills/petrilahdelma/project-spine/project-spine-drift.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.00087 | $0.00969 |
| Opus 5.5 | $0.00035 | $0.00388 |
| Sonnet 5.5 | $0.00017 | $0.00194 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
project-spine-drift 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 1mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift detection and resolution
Goal: determine whether the generated files still match the current inputs, and if not, help the user pick the right fix for each drift category.
Prerequisites
.project-spine/export-manifest.jsonexists. If not, the project was never compiled — switch to project-spine-kickoff.- CLI ≥ 0.8.1.
Step 1 — run the check
From the project root:
spine drift check
Exit codes:
0— clean; nothing to do.1— drift detected; continue.2— can't check (missing manifest, unreadable inputs); investigate before proceeding.
The command prints a summary with three counters and writes drift-report.md + drift-report.json under .project-spine/.
Step 2 — interpret each drift category
Input drift
One or more of: brief.md, design-rules.md, tokens.json, repo profile, or the spine hash itself changed.
Fix: spine compile --brief ./brief.md --repo . (add the same --template, --design, or --tokens the project uses). This regenerates all exports from the new inputs.
The [input:tokens] drift kind fires specifically when the design tokens JSON file (DTCG or Tokens Studio) changed — typical when the design team re-exports from Figma.
Export hand-edits
A generated file (e.g. AGENTS.md) was edited manually after the last compile.
Two valid responses — ask the user which they want:
- "Accept my edits as canonical" → the user wants the hand-edit to survive. They must edit the upstream input (
brief.md,design-rules.md, or the workspace template) so a recompile reproduces the edit. Otherwise the next recompile reverts it. - "Discard my edits, regenerate" → run
spine export --targets allto rewrite the exports from the storedspine.json.
The second option is only safe if the user confirms they don't need the hand-edited text. Never auto-discard.
Missing exports
A file listed in the manifest isn't on disk (deleted, moved, gitignored).
Fix: spine export --targets all to regenerate.
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.
- 1mo ago Changed 3a3eed3496c0
- 1mo ago First seen · 92 lines · 87 tokens per session scan A fdb5a628cebf
project-spine-drift is a skill published in the GitHub repository PetriLahdelma/project-spine (2 stars, last pushed 10d ago), licensed MIT. It adds 87 tokens to every session and 969 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.
loadout-remember
Save a durable, cross-project user preference into loadout's global fragments/profiles — or update the fragment it contradicts. Use when the user states lasting guidance that should follow them across projects and agents ("always X", "never Y", "stop doing Z"), especially when it conflicts with guidance the loadout…