torque:migrate

torque:migrate is a skill for Claude Code, Codex from mattjaikaran/torque. It costs 37 tokens per session (1,309 once invoked), scanned C, original, MIT.

A guide for deciding whether to move from Torque, a workflow that routes work between GSD and Superpowers, to Meridian, its described standalone successor with stored project state and defined commands.

In plain words
What is it for?
Use it to assess whether a project is ready for Meridian and, if so, follow a migration path from Torque.
Why use it?
It helps identify when separate routing is no longer enough, such as when sessions are hard to resume, several milestones or agents are involved, or work must be coordinated remotely.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit Use it to assess whether a project is ready for Meridian and, if so, follow a migration path from Torque.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattjaikaran/torque/migrate
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.

Any agent
npx skills add mattjaikaran/torque --skill migrate
Clone the repo
git clone --depth 1 https://github.com/mattjaikaran/torque

Made for: Claude Code, Codex.

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 torque:migrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattjaikaran/torque/migrate/github.svg)](https://agentmods.dev/skills/mattjaikaran/torque/migrate)
Your own site
<a href="https://agentmods.dev/skills/mattjaikaran/torque/migrate"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/migrate/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.

agentmods 80×15 button for torque:migrate

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattjaikaran/torque/migrate"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,309 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00037 $0.01309
Opus 5.5 $0.00015 $0.00524
Sonnet 5.5 $0.00007 $0.00262
Haiku 4.5 $0.00004 $0.00131

Measured 2mo ago against content hash eaacc432cf67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

torque:migrate scanned grade C with 1 finding 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 2mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ~/.claude/skills/torque
skills/migrate/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrate to Meridian

Evaluate whether the current project would benefit from upgrading to Meridian and provide a migration path.

What is Meridian?

Meridian is the standalone successor to Torque. Instead of routing between GSD and Superpowers, Meridian IS the system — a SQLite-backed state machine with 39 commands, deterministic resume, quality gates, and remote agent dispatch.

When to Migrate

Signals you've outgrown Torque

Run through this checklist. If 3+ are true, Meridian is the right move.

  • Session continuity is painful — you lose context between sessions and /gsd:resume-work isn't enough
  • Multi-milestone project — you've completed 1+ milestones and are starting another
  • Team coordination — multiple people or AI agents need to work on the project
  • You want deterministic resume — same state should produce the exact same prompt every time
  • You need board sync — Linear, Jira, or similar needs to stay in sync with phases
  • Remote execution — you want to dispatch plans to other machines or agents
  • Execution learnings — you want the system to learn from failures and improve over time
  • You're fighting the routing — GSD and SP conflict resolution is becoming overhead

Stay with Torque if

  • Project is simple (< 3 milestones expected)
  • You like GSD and Superpowers separately and just need them coordinated
  • You don't need persistent state beyond .planning/ files
  • Lightweight is a feature, not a limitation

Migration Path

Step 1: Install Meridian

git clone https://github.com/mattjaikaran/meridian.git ~/.claude/skills/meridian

Step 2: Initialize in your project

# In your project directory
# Meridian will detect existing .planning/ and offer to import

Then run /meridian:init — it creates .meridian/state.db and imports existing state.

Step 3: Map your workflow

Torque (GSD + SP) Meridian equivalent
/gsd:new-project /meridian:init
/gsd:discuss-phase /meridian:discuss
/gsd:spec-phase /meridian:discuss (spec built-in)
/gsd:plan-phase /meridian:plan
/gsd:execute-phase /meridian:execute
/gsd:verify-work /meridian:verify-phase
/gsd:validate-phase /meridian:verify-phase (Nyquist built-in)
/gsd:resume-work /meridian:resume (deterministic)
/gsd:quick /meridian:quick
/gsd:fast /meridian:fast
/gsd:ship /meridian:ship
/gsd:pr-branch /meridian:pr-branch
/gsd:autonomous /meridian:autonomous
/gsd:insert-phase /meridian:insert-phase
/gsd:remove-phase /meridian:remove-phase
/gsd:undo /meridian:revert
requesting-code-review /meridian:review (two-stage)
receiving-code-review /meridian:review (handles both sides)
systematic-debugging /meridian:debug (with KB)
/gsd:note /meridian:note
/gsd:plant-seed /meridian:seed
/gsd:session-report /meridian:report
/torque:status /meridian:status or /meridian:dashboard
/torque:next /meridian:next

Read the full file on GitHub · 128 lines

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. 2mo ago First seen · 128 lines · 37 tokens per session scan C eaacc432cf67

Subscribe to this mod's changes

torque:migrate is a skill published in the GitHub repository mattjaikaran/torque (6 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,309 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

contract-and-proposal-writer

Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…

alirezarezvani/claude-skills · 106 tokens

vpe-advisor

VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…

alirezarezvani/claude-skills · 130 tokens

chief-data-officer-advisor

Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…

alirezarezvani/claude-skills · 131 tokens

general-counsel-advisor

General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…

alirezarezvani/claude-skills · 114 tokens

strategic-alignment

Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…

alirezarezvani/claude-skills · 92 tokens

executive-mentor

Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually…

alirezarezvani/claude-skills · 69 tokens