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 mattjaikaran/torque --skill nextgit 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/next)<a href="https://agentmods.dev/skills/mattjaikaran/torque/next"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/next/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/mattjaikaran/torque/next"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/next.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.00036 | $0.00970 |
| Opus 5.5 | $0.00014 | $0.00388 |
| Sonnet 5.5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
torque:next 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 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.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Torque Next Action
Analyze project state and recommend exactly ONE next command. Think of this as a GPS for your development workflow.
Procedure
Step 1: Gather state
Same as /torque:status — read .planning/, docs/plans/, git state. But don't output the full status. Focus on determining the current position.
Step 2: Decision tree
Work through this tree top-to-bottom. First match wins.
1. Is there an active bug or failing test?
→ `systematic-debugging`
Why: Bugs block everything. Fix first.
2. Does .planning/ exist?
├─ YES (GSD project):
│ a. Is there a HANDOFF.md in the active phase?
│ → `/gsd:resume-work`
│ Why: Paused work should be resumed before starting new work.
│
│ b. Is STATE.md showing a phase in "executing" with incomplete plans?
│ → `/gsd:execute-phase` (continue)
│ Why: Finish what you started.
│
│ c. Is a phase complete but not verified?
│ → `/gsd:verify-work`
│ Why: Verification before review.
│
│ d. Is a phase verified but not code-reviewed?
│ → `requesting-code-review`
│ Why: GSD has no review step — SP fills the gap.
│
│ e. Is a phase reviewed but not shipped?
│ → `/gsd:ship` or `/gsd:pr-branch`
│ Why: Ship cleanly — filters .planning/ commits from PR.
│
│ f. Are all phases in the current milestone complete?
│ → `/gsd:audit-milestone` then `/gsd:complete-milestone`
│ Why: Close out the milestone properly.
│
│ g. Is the next phase planned but not started?
│ → `/gsd:execute-phase`
│ Why: Plans exist, execute them.
│
│ h. Is the next phase discussed and spec'd but not planned?
│ → `/gsd:plan-phase`
│ Why: Context and spec exist, create plans.
│
│ h2. Is the next phase discussed but not spec'd (ambiguous scope)?
│ → `/gsd:spec-phase`
│ Why: Lock falsifiable requirements before planning.
│
│ i. Is there a next phase that hasn't been discussed?
│ → `/gsd:discuss-phase`
│ Why: Gather context before planning.
│
│ i2. Is this an AI/LLM phase that hasn't been designed?
│ → `/gsd:ai-integration-phase`
│ Why: Produce AI-SPEC.md with framework + eval strategy.
│
│ j. No more phases in roadmap?
│ → `/gsd:new-milestone` or project complete
│
└─ NO (no .planning/):
a. Does docs/plans/ exist with incomplete plans?
→ Re-read plans, continue execution
Why: Pick up where you left off.
b. No workflow state at all?
→ Ask: "New project or standalone feature?"
→ New project: `/gsd:new-project`
→ Existing codebase: `/gsd:map-codebase`
→ Quick standalone: `brainstorming`
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.
- 2mo ago First seen · 109 lines · 36 tokens per session scan A db56dcfd039c
torque:next is a skill published in the GitHub repository mattjaikaran/torque (6 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 970 once invoked, about $0.0001 per session on Opus 5.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
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…
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…
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…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
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…
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…