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 checkgit 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/check)<a href="https://agentmods.dev/skills/mattjaikaran/torque/check"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/check/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/check"><img src="https://agentmods.dev/badge/skills/mattjaikaran/torque/check.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.00034 | $0.00830 |
| Opus 5.5 | $0.00014 | $0.00332 |
| Sonnet 5.5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade C, and why
torque:check scanned grade C with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/get-shit-done/VERSION 2>/dev/null || echo "GSD_VERSION=unknown" Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls ~/.claude/skills/gsd-* 2>/dev/null | head -5 How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Torque Health Check
Verify that GSD and Superpowers are installed correctly and the current project has no configuration conflicts.
Procedure
Step 1: Check GSD installation
# Check for GSD tools
ls ~/.claude/get-shit-done/bin/gsd-tools.cjs 2>/dev/null && echo "GSD_INSTALLED=true" || echo "GSD_INSTALLED=false"
# Get GSD version
cat ~/.claude/get-shit-done/VERSION 2>/dev/null || echo "GSD_VERSION=unknown"
# Check GSD skills are registered
ls ~/.claude/skills/gsd-* 2>/dev/null | head -5
Step 2: Check Superpowers installation
# Check for core SP skills (required)
for skill in systematic-debugging test-driven-development brainstorming writing-plans subagent-driven-development requesting-code-review verification-before-completion finishing-a-development-branch receiving-code-review; do
if ls ~/.claude/skills/$skill/SKILL.md 2>/dev/null > /dev/null; then
echo " ✓ $skill"
else
echo " ✗ $skill (MISSING)"
fi
done
# Check for extended SP skills (optional but recommended)
echo ""
echo "Extended skills:"
for skill in grill-me improve-codebase-architecture write-a-prd prd-to-issues changelog-generator webapp-testing playwright-skill ci-cd monitoring-observability; do
if ls ~/.claude/skills/$skill/SKILL.md 2>/dev/null > /dev/null; then
echo " ✓ $skill"
else
echo " ○ $skill (optional, not installed)"
fi
done
Step 3: Check Torque installation
# Verify this skill is properly installed
ls ~/.claude/skills/torque/SKILL.md 2>/dev/null && echo "TORQUE_INSTALLED=true" || echo "TORQUE_INSTALLED=false"
Step 4: Project-level checks
Run these checks in the current working directory:
- Mixed plan locations: Flag if both
.planning/ANDdocs/plans/exist - Orphaned .planning/: Flag if
.planning/exists but has noPROJECT.md(manually created) - Stale state: Flag if
.planning/STATE.mdreferences a phase that doesn't have a directory - Missing reviews: Flag if any phase has
VERIFICATION.mdbut no code review was done (check git log for review commits)
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 · 103 lines · 34 tokens per session scan C fb30d80b13cc
torque:check is a skill published in the GitHub repository mattjaikaran/torque (6 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 830 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Find the root cause of Elixir/Phoenix bugs — crashes, exceptions, stack traces, compile errors, LiveView that won't update, silent failures. Use when something is broken or misbehaves. --parallel for 4 tracks.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
perf
Use when anything in a Phoenix app is slow, times out, or uses too much memory, even if the cause looks obvious. Load it before analyzing or fixing: it runs measured Ecto, LiveView and OTP checks and ranks fixes.