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/mattjaikaran/torque/migratenpx skills add mattjaikaran/torque --skill migrategit clone --depth 1 https://github.com/mattjaikaran/torqueWrote 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/mattjaikaran/torque/migrate)<a href="https://agentmods.dev/skills/mattjaikaran/torque/migrate"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/migrate.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01309 |
| Opus 5 | $0.00018 | $0.00655 |
| Sonnet 5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
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 3d 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 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-workisn'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 |
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.
- 3d ago First seen · 128 lines · 37 tokens per session scan C eaacc432cf67
torque:migrate is a skill published in the GitHub repository mattjaikaran/torque (6 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,309 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
muapi-media-editing
Edit and enhance images and videos with AI via muapi.ai — prompt-based editing, upscaling, background removal, face swap, lipsync, video effects, and more.
ctf-malware
Provides malware analysis and network traffic techniques for CTF challenges. Use when analyzing obfuscated scripts, malicious packages, custom crypto protocols, C2 traffic, PE/.NET binaries, RC4/AES encrypted communications, YARA rules, shellcode analysis, memory forensics for malware (Volatility malfind, process…
research
Conduct preliminary research on a topic and generate research outline. For academic research, benchmark research, technology selection, etc.
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.