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/statusnpx skills add mattjaikaran/torque --skill statusgit 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/status)<a href="https://agentmods.dev/skills/mattjaikaran/torque/status"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/status.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.00043 | $0.00761 |
| Opus 5 | $0.00022 | $0.00380 |
| Sonnet 5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
torque:status 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 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.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Torque Status
Show the developer a unified view of their project state. No database — read files and git only.
Procedure
Step 1: Detect project type
# Check which system is active
ls -d .planning/ 2>/dev/null && echo "GSD_PROJECT=true" || echo "GSD_PROJECT=false"
ls -d docs/plans/ 2>/dev/null && echo "SP_PROJECT=true" || echo "SP_PROJECT=false"
Step 2: GSD project state (if .planning/ exists)
Read these files in order (skip any that don't exist):
.planning/STATE.md— current phase, plan statuses, blockers.planning/ROADMAP.md— milestone and phase overview.planning/PROJECT.md— project goals and tech stack (first 30 lines)- Active phase directory — check
.planning/phases/N/for the current phase:CONTEXT.md— what this phase is aboutPLAN.mdorPLAN-*.md— execution plans and their statusSUMMARY.mdfiles — completed plan summariesVERIFICATION.md— verification results if phase is in verify stageHANDOFF.md— if work was paused mid-phase
Step 3: SP standalone state (if docs/plans/ exists, no .planning/)
- Read all
docs/plans/*.mdfiles - Check for completion markers (checked boxes
[x]vs unchecked[ ]) - Identify current position in the plan
Step 4: Git context
git branch --show-current
git log --oneline -5
git status --short
Step 5: Conflict detection
Flag if BOTH .planning/ AND docs/plans/ exist — this is a misconfiguration. See references/conflict-resolution.md.
Step 6: Output format
Print a structured summary:
## Project Status
**Type**: GSD project | SP standalone | No workflow detected
**Branch**: feature/xyz
**Phase**: 3 of 7 — "Authentication system"
**Phase status**: executing (2/4 plans complete)
**Blockers**: None | [list blockers]
**Last activity**: 2h ago — "add jwt middleware"
### Active Plans
- [x] PLAN-01: Database schema (complete)
- [x] PLAN-02: Auth service (complete)
- [ ] PLAN-03: JWT middleware (in progress)
- [ ] PLAN-04: Route guards (pending)
### Suggested Next Action
→ Continue executing PLAN-03, or run `/gsd:resume-work` if context was lost
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 · 95 lines · 43 tokens per session scan A c76fcd961ba4
torque:status is a skill published in the GitHub repository mattjaikaran/torque (6 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 761 once invoked, about $0.0002 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-31.
Other skills, from other repositories
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
ln-51-opportunity-evaluator
Evaluates new product directions using current demand, acquisition, competition, economics, and validation evidence. Use before commitment; not for backlog or implementation planning.
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
pm-prioritize
Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do…