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 agents/pilotwaffle/torqclaw/readmegit clone --depth 1 https://github.com/pilotwaffle/TORQCLAWWhat 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.00000 | $0.01094 |
| Opus 5 | $0.00000 | $0.00547 |
| Sonnet 5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
README 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TorqClaw agent routing policy
Adapted from the TORQ Console harness (E:\TORQ-CONSOLE\.claude\agents).
These are TorqClaw-local definitions. The Console harness drives a different
product through .torq/launch/* watcher scripts and hardcoded
E:\TORQ-CONSOLE\... paths; running those agents against this repo would read
specs from and write verdicts into the wrong product. What is ported here is the
discipline, re-pathed to E:\TorqClaw.
Roles and model assignments (operator-set, 2026-08-09)
| Role | Model | Responsibility |
|---|---|---|
| G1D / planner / router | Fable-5 | Orchestrate. Scope the ticket, route work, hold the sequence. Does not implement. |
| G1R / reviewer | Opus 4.7 | Independent review when design, architecture, risk, or security is involved. Reviews the SPEC before the Builder spends compute. |
| Builder | Sonnet 5 | Implement the spec precisely. Does not design or approve. |
| G2A / final verifier | Opus 4.8 | Grade high-impact changes against files, tests, build output, git state, and acceptance criteria. Sole authority to authorize a push. |
| Cheap verification | Haiku / fast | Checklist grading, log triage, scope sanity checks. Never sole final authority for risky code, merges, security, production, or architecture. |
| Memory-writer | — | Updates STATE.md / MEMORY.md only after meaningful progress, tests pass, and verifier/G2A passes. |
Hard rules
- Do not stop until tests pass and verifier/G2A passes — unless blocked by missing authority, unsafe repo state, permission limits, or an operator-required decision.
- Never push, merge, delete, clean, reset, overwrite operator files, or run destructive commands without explicit operator approval. G2A approval is a technical precondition for a push, not operator authorization.
- Project-local
CLAUDE.md,MEMORY.md,.claude/agents, hooks, and workflows are the active authority.
Two practices worth keeping from the Console harness
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 · 78 lines · 0 tokens per session scan A a781d3c65c47
README is an agent published in the GitHub repository pilotwaffle/TORQCLAW (4 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,094 tokens. 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 agents, from other repositories
workflow-spec
RagCode Agent Workflows orchestrate multiple AI agents (codex, claude, gemini, grok, or any CLI in .ragcode/agents/agents.json) through a validated DAG. A workflow is a JSON file: explicit, reviewable, and validation-friendly.
cli-adapters
RagCode orchestrates AI agents by spawning their CLIs. Vendor CLI syntax drifts, so built-in command templates are presets, not hard-coded protocol truth. Anything can be overridden per-repo via .ragcode/agents/agents.json.
Dashboard Dev
Agent "Dashboard Dev" from shawnhack/exocortex, covering dashboard dev, core responsibilities, key files, coding constraints and escalation.
Memory Engineer
Agent "Memory Engineer" from shawnhack/exocortex, covering memory engineer, core responsibilities, key files, coding constraints and escalation.
MCP Developer
Agent "MCP Developer" from shawnhack/exocortex, covering mcp developer, core responsibilities, key files, coding constraints and escalation.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.