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-kickoffgit 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-kickoff)<a href="https://agentmods.dev/skills/petrilahdelma/project-spine/project-spine-kickoff"><img src="https://agentmods.dev/badge/skills/petrilahdelma/project-spine/project-spine-kickoff/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-kickoff"><img src="https://agentmods.dev/badge/skills/petrilahdelma/project-spine/project-spine-kickoff.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.00084 | $0.01389 |
| Opus 5 | $0.00042 | $0.00694 |
| Sonnet 5 | $0.00017 | $0.00278 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
project-spine-kickoff 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 11d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kickoff flow for a new project
Goal: produce the 21 canonical Project Spine files (AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, .cursor/rules/project-spine.mdc, plus scaffold/QA/rationale docs) from a real brief + the current repo.
Prerequisites — check before proceeding
- CLI installed:
spine --versionreturns0.9.2-beta.0or later - Current directory is the project root (has
package.jsonor equivalent) - No
.project-spine/directory yet (if there is, this is probably a drift scenario — switch to project-spine-drift)
Step 1 — pick a template (optional but strongly recommended)
List available starter templates:
spine template list
Bundled templates cover these project types:
saas-marketing— marketing site (hero, pricing, customer pages, compliance)app-dashboard— authenticated product with data tables, settings, role gatingdesign-system— component library, tokens, Storybookdocs-portal— technical documentation siteapi-service— Node / TypeScript API service with health and readiness probesmonorepo— pnpm / Turborepo / Nx workspace guidance
If the user mentions one of these project types, pick the matching template. If they describe something unusual (extension, CLI tool, data pipeline), skip the template and compile without it — the brief carries the intent.
Step 2 — scaffold
spine init --template <template-name>
# or, without a template:
spine init
This creates:
brief.mdat the repo root, with prompts for each section (Goals, Audience, Constraints, Assumptions, Risks, Success criteria).project-spine/directory for outputs
Step 3 — ask the user for brief content
Do not fill the brief yourself from general knowledge. Ask the user directly:
I scaffolded a brief at
brief.md. To generate useful agent instructions I need your help filling a few sections. Could you tell me:
- What are the 3–5 core goals for this project? (measurable, not aspirational)
- Who is the audience? (role, scale, prior tools)
- Any hard constraints? (stack, compliance, budget)
- What's out of scope that you want agents to not touch?
I'll fill the rest from the repo analysis.
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.
- 11d ago First seen · 111 lines · 84 tokens per session scan A bda5631e57d0
project-spine-kickoff is a skill published in the GitHub repository PetriLahdelma/project-spine (2 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 1,389 once invoked, about $0.0004 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.
Other skills, from other repositories
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
hooksmith
Use when designing or reviewing safe Grok Build hooks for linting, tests, formatting, notifications, command guards, lifecycle automation, or project hook trust decisions.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
architecture-review
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
frontend-ux-engineer
Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.