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/prompt-auditnpx skills add Megaprompting/torque-loop --skill prompt-auditgit 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.00084 | $0.00654 |
| Opus 5 | $0.00042 | $0.00327 |
| Sonnet 5 | $0.00017 | $0.00131 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
prompt-audit 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ratchet:prompt-audit — the library as an OS
A prompt library is not a pile of good words; it is an operating system for cognition. This command audits it as one. It does not rewrite prompts first — it diagnoses the system: what work each prompt does, which moves are missing, and where the library lets the model escape into elegant analysis instead of producing something.
Step 0 — Load the library
Take the prompt list from the argument, a file, or the current context. Do not rewrite yet.
Classify
Tag each prompt by the type of work it performs (a prompt may do more than one):
- target locking · diagnosis · artifact production · adversarial testing · decision · patching · memory/state · orchestration · compression · boundary pushing
Find the system's shape
- Overrepresented moves — where the library is thick (usually diagnosis and "next move" prompts).
- Missing moves — where it is thin (usually artifact production, patching, testing, serialized state).
- Meta-looping prompts — those that ask what to ask next without ever forcing a move. These are the hallway of mirrors.
- Artifact-producing prompts — the ones that actually leave something behind.
- Prompts to delete or merge — redundant, vague, or low-consequence.
- The minimum new prompt set that would outperform the current library.
The operating rule
Judge every prompt against this bar. Keep it only if it does at least one:
- Forces a choice. 2. Creates an artifact. 3. Tests an artifact. 4. Patches a defect.
- Serializes useful state. 6. Kills a bad option. 7. Pushes to a higher-yield move.
Everything else is smoke.
Output contract
CLASSIFICATION: <table: prompt → work type(s)>
OVERREPRESENTED: <moves the library over-does>
MISSING: <moves it lacks — the expensive gaps>
META-LOOPERS: <prompts that never force a move>
DELETE / MERGE: <the cuts>
UPGRADED SET (sequenced workflow, not a pile):
1. <prompt> — <the move it forces>
2. ...
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 · 66 lines · 84 tokens per session scan A 1c2a1abf87ba
prompt-audit is a skill published in the GitHub repository Megaprompting/torque-loop (5 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 654 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
omh-llm-app-dev
This is a Hermes-native llm-app-dev workflow skill.
novel-tools
网文创作工具与生产流程。当用户需要使用AI辅助写作工具、设计提示词模板、规划写作工作流、选择码字工具、制定发布与数据分析策略时触发。覆盖DeepSeek/ChatGPT/Claude/豆包等AI工具应用、提示词工程、工作流设计、发布运营。.
prompt-architect
Analyzes and improves prompts using 31 frameworks across 7 intent categories. Use when a user wants to improve, rewrite, structure, or engineer a prompt — including requests like "help me write a better prompt", "improve this prompt", "what framework should I use", "make this prompt more effective", or any prompt…
cco-coach
Analyze the user's last prompt for clarity, scope and specificity — give a quality score and concrete suggestions to make the next prompt produce better results.
happyhorse-prompt-studio
Interactive prompt studio for HappyHorse 1.0 video generation. Guides users through scenario discovery with vivid examples, then assembles production-ready prompts in JP/CN/EN. Use when someone wants to create AI video content with HappyHorse but doesn't know where to start, or when they have a specific scenario and…
refine-prompt
Transforms vague prompts into precise, structured AI instructions. Use when asked to refine, improve, or sharpen a prompt, do prompt engineering, write a system prompt, or make AI instructions more effective.