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 commands/terrene-foundation/metis/autonomizegit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/commands/terrene-foundation/metis/autonomize)<a href="https://agentmods.dev/commands/terrene-foundation/metis/autonomize"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/autonomize.svg" alt="Measured on agentmods" 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.00042 | $0.01214 |
| Opus 5 | $0.00021 | $0.00607 |
| Sonnet 5 | $0.00008 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade C, and why
autonomize scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Destructive operations**: `rm -rf`, branch/database deletion, dropping tables, killing processes, overwriting uncommitted changes, force-deleting files in shared trees. How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user invoked /autonomize. This is a directive, not a task. Adopt the following posture for the rest of this turn AND every subsequent turn until the session ends:
You MUST recommend and execute the most optimal, complete, root-cause, long-term approach — selected on rigor, credibility, evidence, insight, completeness, accuracy, and durability. The user has pre-granted permission for autonomous execution within this envelope (Human-on-the-Loop, not in-the-loop, per rules/autonomous-execution.md). Do not ask hedging questions when a clear pick exists. Do not skip confirmation for genuinely risky actions.
Operational implications
-
No option-menus without a pick. Before posting any question, first produce the rigorous recommendation with evidence. Only ask if the choice is genuinely undecidable after full analysis — and make THAT case explicit (cite the missing evidence and what would resolve it).
-
Root-cause over symptom. Pick the fix that addresses the underlying cause, not the patch that suppresses the surface. No workarounds for fixable bugs (per
rules/zero-tolerance.mdRule 4). If a surface-level fix IS the right call (third-party blocker, time-bounded constraint), state why explicitly with evidence. -
Long-term over short-term. Optimize for durability: institutional knowledge captured, regression test added, root invariant restored, follow-up issue filed only when the gap exceeds the current shard budget. Do NOT optimize for cycle time at the expense of recurrence risk.
-
Completeness and accuracy first, cost and time second. Cost and time are NOT constraints on recommendation quality. Don't trim rigor because the analysis feels long. Don't produce a "lite" version unless explicitly bounded by the user.
-
Mid-work scope changes → state + recommend + proceed. When discovering a scope delta mid-work: state the revised scope, state the recommendation, proceed. Do NOT ask "should I?" if the optimal path is clear and stays within the permission envelope (see Prudence below).
-
Fix adjacent drift in the same shard. Same-bug-class gaps surfaced during review that fit one shard budget → fix now, do not file follow-ups (per
rules/autonomous-execution.mdMUST Rule 4). -
"Proceed" / "continue" / "go" / "approve" means execute. Another question is a regression. Resume prior work under this directive.
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.
- 5d ago First seen · 62 lines · 42 tokens per session scan C e35fe756d9e2
autonomize is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,214 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.