skill-forge

A workflow for adding or changing a Ratchet command across all the project files that describe and check it. Ratchet commands are project-specific development steps such as planning or testing routines.

In plain words
What is it for?
Use it when creating a new Ratchet skill or changing an existing one. It updates the command prompt, skill instructions, README catalogue, templates when needed, and shape tests.
Why use it?
It prevents the command's instructions, documentation, templates, and automated checks from drifting apart. Changing only one copy can leave the project inconsistent.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/megaprompting/torque-loop/skill-forge
Any agent
npx skills add Megaprompting/torque-loop --skill skill-forge
Clone the repo
git clone --depth 1 https://github.com/Megaprompting/torque-loop

Made for: Claude Code, Codex.

Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,168 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00090 $0.01168
Opus 5 $0.00045 $0.00584
Sonnet 5 $0.00018 $0.00234
Haiku 4.5 $0.00009 $0.00117

Measured 2d ago against content hash 9f6fbfb72569, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skill-forge 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.

.claude/skills/skill-forge/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/skill-forge — one command, every surface

A /ratchet:* command is not a file; it is a contract spread across four synced surfaces — reference/PROMPTS.md (intent), skills/<name>/SKILL.md (procedure), README.md (catalog), and test/plugin-shape.test.js (drift police) — plus templates/ when the command produces a file-shaped record. Editing one surface and not the others is the repo's most common failure mode. This skill walks them in dependency order: intent first, procedure second, catalog third, guard last.

Step 0 — Ground truth

ls skills/
grep -n "<command-name>" reference/PROMPTS.md README.md test/plugin-shape.test.js

Read the two nearest-neighbor skills (for a gate-like command: skills/map/SKILL.md, skills/build/SKILL.md) — the new skill must read like it was written the same day.

Step 1 — Canonical prompt (PROMPTS.md) — the source of truth, written FIRST

  • Add the prompt as a fenced text block in reference/PROMPTS.md, in the imperative copy-paste voice of the existing twelve ("Produce the artifact now." / "Map the fog before you build.").
  • Add a row to the Command ↔ prompt map table.
  • If the mechanism is grafted from elsewhere: general mechanism, own words — rewrite in ratchet vocabulary and note provenance (aperture-dial precedent).
  • Rule to preserve: the prompt must force pressure — a choice, an artifact, a test, a patch, serialized state, a killed option, or a push. If it only produces insight, it is not a ratchet command; stop and say so.

Step 2 — SKILL.md in the house shape

skills/<name>/SKILL.md, exactly this skeleton:

---
name: <name>
description: <verb-first pitch. Use when <trigger>. <what it produces / refuses>.>
argument-hint: "[...]"        # only if it takes arguments
---

# /ratchet:<name> — <tagline>

<2–3 sentences: why this command exists, what failure it prevents.>

## Step 0 — Load state

ratchet status


## Procedure
<numbered, imperative, bolded key rules. Prompt-level tripwires welcome, but never
claim they are enforced — enforcement is the CLI's job.>

## Output contract

<FIXED-SHAPE block — same sections every run, emptiness stated>


## Serialize

ratchet <exact commands — artifact add / state append / state set phase>


<closing line naming the NEXT move — no ratchet skill ends in analysis.>

Read the full file on GitHub · 120 lines

Changes

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.

  1. 2d ago First seen · 120 lines · 90 tokens per session scan A 9f6fbfb72569

Subscribe to this mod's changes

skill-forge is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,168 once invoked, about $0.0005 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.

Related

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…

os-factory/har · 89 tokens

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…

os-factory/har · 101 tokens

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"…

os-factory/har · 110 tokens

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…

agentis-tools/ctx · 60 tokens

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…

agentis-tools/ctx · 60 tokens

golden-rss

Use when testing the rss golden build.

yusufkaraaslan/Skill_Seekers · 12 tokens