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/jketreno/clare/update-autonomygit clone --depth 1 https://github.com/jketreno/clareWrote 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/jketreno/clare/update-autonomy)<a href="https://agentmods.dev/commands/jketreno/clare/update-autonomy"><img src="https://agentmods.dev/badge/commands/jketreno/clare/update-autonomy.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 | $0.00000 | $0.00360 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
update-autonomy 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 4d 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.
What it actually says
/project:update-autonomy — Guide autonomy boundary update
Guides the user through updating clare/autonomy.yml to add, modify, or remove an autonomy boundary.
Instructions
-
First, read and display the current contents of
clare/autonomy.yml -
Ask the user:
- What path are they adding/modifying? (e.g.,
src/billing) - What level? (
full-autonomy/supervised/humans-only) - Why? (reason for this boundary)
- Add, modify, or remove the entry?
- What path are they adding/modifying? (e.g.,
-
Show the proposed YAML change before applying it:
# Proposed addition to clare/autonomy.yml modules section:
- path: "[path]"
level: [level]
reason: "[reason]"
- Ask for confirmation: "Apply this change to
clare/autonomy.yml?" - On confirmation, edit
clare/autonomy.ymlto add/modify/remove the entry - Confirm: "Updated
clare/autonomy.yml. The[path]path is now[level]."
Guidance for Choosing Levels
Suggest based on path characteristics:
- full-autonomy: Generated code, pure utilities, test fixtures, anything fully derived from a source of truth
- supervised: Business logic, API handlers, database queries, UI components with business rules
- humans-only: Money movement, authentication, cryptography, core domain models, regulatory compliance code
After Updating
Remind the user: "Consider adding an architecture test that validates this boundary is respected. See clare/templates/architecture-tests/autonomy-guard.test.js for an example."
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.
- 4d ago First seen · 37 lines · 0 tokens per session scan A 7b6062df4eed
update-autonomy is a command published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 360 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.