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 agentmods add skills/patricksys/workspine/distillednpx skills add PatrickSys/workspine --skill distilledgit clone --depth 1 https://github.com/PatrickSys/workspineWhat 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 | $0.00024 | $0.00869 |
| Opus 5 | $0.00012 | $0.00434 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
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.
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.mdby embeddingdistilled/workflows/*.md, plus repo-local deterministic helpers at.work/bin/gsdd.mjs(or.planning/bin/gsdd.mjsin legacy workspaces). - Optional: generates tool adapters (root
AGENTS.md, Claude.claude/skills+.claude/commandsalias +.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.mdas the primary integration path. - Root
AGENTS.mdis 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
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.
- DESIGN.md 277 KB
- EVIDENCE-INDEX.md 41 KB
- README.md 14 KB
- references/observation-record.md 2.1 KB
- references/proof-rules.md 2.7 KB
- templates/agents.block.md 1.8 KB
- templates/agents.md 84 B
- templates/approach.md 8.2 KB
- templates/auth-matrix.md 3.5 KB
- templates/brownfield-change/CHANGE.md 5.0 KB
- templates/brownfield-change/HANDOFF.md 1.6 KB
- templates/brownfield-change/VERIFICATION.md 2.0 KB
- templates/codebase/architecture.md 3.2 KB
- templates/codebase/concerns.md 2.8 KB
- templates/codebase/conventions.md 6.7 KB
- templates/codebase/stack.md 2.5 KB
- templates/delegates/approach-explorer.md 2.2 KB
- templates/delegates/mapper-arch.md 1.9 KB
- templates/delegates/mapper-concerns.md 1.8 KB
- templates/delegates/mapper-quality.md 2.1 KB
- templates/delegates/mapper-tech.md 1.6 KB
- templates/delegates/plan-checker.md 11 KB
- templates/delegates/researcher-architecture.md 1.9 KB
- templates/delegates/researcher-features.md 1.9 KB
- templates/delegates/researcher-pitfalls.md 1.8 KB
- templates/delegates/researcher-stack.md 1.9 KB
- templates/delegates/researcher-synthesizer.md 1.8 KB
- templates/research/architecture.md 1.2 KB
- templates/research/features.md 663 B
- templates/research/pitfalls.md 1.2 KB
- templates/research/stack.md 1.2 KB
- templates/research/summary.md 2.5 KB
- templates/roadmap.md 2.1 KB
- templates/spec.md 3.7 KB
- templates/ui-proof.md 5.0 KB
- workflows/audit-milestone.md 16 KB
- workflows/complete-milestone.md 15 KB
- workflows/execute.md 30 KB
- workflows/map-codebase.md 12 KB
- workflows/new-milestone.md 11 KB
- workflows/new-project.md 27 KB
- workflows/pause.md 8.7 KB
- workflows/plan.md 43 KB
- workflows/progress.md 21 KB
- workflows/quick.md 22 KB
- workflows/resume.md 20 KB
- workflows/verify-work.md 7.4 KB
- workflows/verify.md 28 KB
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.
- 2d ago First seen · 90 lines · 24 tokens per session scan A 8b82be56b1fd
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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…
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.
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.