Workspine

A repository-based workflow for AI-assisted software development that moves from a written specification to implementation and verification.

In plain words
What is it for?
Use it to initialize a project workspace, plan and execute milestones, verify changes, audit progress, and complete or start new milestones.
Why use it?
It gives development work a repeatable structure and keeps plans, phases, research, and checks in the project itself.

Skill for Claude CodeCodex

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 skills/patricksys/workspine/distilled
Any agent
npx skills add PatrickSys/workspine --skill distilled
Clone the repo
git clone --depth 1 https://github.com/PatrickSys/workspine

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 869 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.00024 $0.00869
Opus 5 $0.00012 $0.00434
Sonnet 5 $0.00005 $0.00174
Haiku 4.5 $0.00002 $0.00087

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

Security

Grade A, and why

Workspine 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 2d 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.

distilled/SKILL.md · 90 lines

What it actually says

init -> [plan -> execute -> verify] x N phases -> done

Read only the file for the phase you are in:

  • new-project: workflows/new-project.md
  • plan: workflows/plan.md
  • execute: workflows/execute.md
  • verify: workflows/verify.md
  • audit-milestone: workflows/audit-milestone.md
  • complete-milestone: workflows/complete-milestone.md
  • new-milestone: workflows/new-milestone.md
  • quick: workflows/quick.md

<project_structure> Workspine uses .work/ as the durable workspace. Legacy .planning/ workspaces are still read and supported.

.work/
  SPEC.md
  ROADMAP.md
  config.json
  templates/
  phases/
  research/

</project_structure>

npx -y workspine init
npx -y workspine init --tools claude
npx -y workspine init --tools codex
npx -y workspine init --tools agents

Behavior:

  • Always: generates open-standard skills at .agents/skills/work-*/SKILL.md by embedding distilled/workflows/*.md, plus repo-local deterministic helpers at .work/bin/gsdd.mjs (or .planning/bin/gsdd.mjs in legacy workspaces).
  • Optional: generates tool adapters (root AGENTS.md, Claude .claude/skills + .claude/commands alias + .claude/agents, OpenCode .opencode/commands + .opencode/agents, Codex CLI .codex/agents/work-plan-checker.toml).
  • Codex CLI: uses the portable skill entry surface and the generated .codex/agents/ checker/approach-explorer agents; it does not use .codex/AGENTS.md as the primary integration path.
  • Root AGENTS.md is only written when explicitly requested (so we do not pollute existing user governance).

Core:

  • .work/templates/spec.md -> .work/SPEC.md
  • .work/templates/roadmap.md -> .work/ROADMAP.md

Research:

  • .work/templates/research/*.md -> .work/research/*.md

Brownfield codebase mapping:

  • .work/templates/codebase/*.md -> .work/codebase/*.md
Files

What ships with it

48 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 90 lines · 24 tokens per session scan A 8b82be56b1fd

Subscribe to this mod's changes

Workspine is a skill published in the GitHub repository PatrickSys/workspine (57 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 869 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens