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/megaprompting/torque-loop/release-cutnpx skills add Megaprompting/torque-loop --skill release-cutgit clone --depth 1 https://github.com/Megaprompting/torque-loopWhat 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.00072 | $0.01479 |
| Opus 5 | $0.00036 | $0.00740 |
| Sonnet 5 | $0.00014 | $0.00296 |
| Haiku 4.5 | $0.00007 | $0.00148 |
Grade A, and why
release-cut 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release-cut — the release ritual, mechanized
Six releases (0.2 → 0.7) followed the identical multi-file ritual by hand. Every step below has drifted at least once in some repo somewhere; the plugin-shape suite catches most drift, but only after you've made it. This skill makes the ritual deterministic. Hard boundary: this skill ends at an open PR. Merge, tag, and GitHub Release are Danny's verbs, every time.
Step 0 — Preconditions (refuse to start if any fails)
git status # no unrelated TRACKED change staged or modified
git log --oneline -5
npm test # must be green BEFORE the cut — broken-world rule
"Clean" means no unrelated tracked change. Untracked scratch (.claude/worktrees/,
sandbox dirs) is normal here and is not a reason to stop — Step 5 stages by name so it
cannot reach the commit. Do not "tidy" it by deleting someone's worktree.
- CHANGELOG
[Unreleased]is non-empty. An empty [Unreleased] means there is nothing to release — say so and stop. - Version
X.Y.Zand<codename>are given as arguments, or STOP and ask. Never invent a codename: each release names a gate concept ("Probe Gate", "Fog Gate") and Danny picks it. - You are on
mainor the feature branch that carries the work. Note which.
Step 1 — Branch
git checkout -b release/vX.Y.Z-<codename-slug>
Slug is kebab-case (0.7.0 + "Probe Gate" → release/v0.7.0-probe-gate).
Step 2 — Bump the five version fields (four files)
| File | Field(s) |
|---|---|
package.json |
version |
.claude-plugin/plugin.json |
version |
.claude-plugin/marketplace.json |
metadata.version AND plugins[0].version |
.codex-plugin/plugin.json |
version |
Both CLIs derive their --version from package.json — do not touch src.
Then sweep README for version surfaces:
grep -n "ratchet [0-9]\+\.[0-9]\+\.[0-9]\+" README.md
Every -> ratchet X.Y.Z example must show the new version (plugin-shape enforces this).
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.
- 2d ago First seen · 132 lines · 72 tokens per session scan A 04b8adb5eb14
release-cut is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,479 once invoked, about $0.0004 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
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
factory-line
Factory line for executing one station of a declared multi-station program — read the installed line bundle (har line status), plan parallel work into isolated HAR slots, run the cumulative gate with har line gate, and hand off for human review. Use when asked to "run a factory line", "run the next station", "execute…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
golden-rss
Use when testing the rss golden build.