Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/obeone/claude-skills/automode-edit)<a href="https://agentmods.dev/commands/obeone/claude-skills/automode-edit"><img src="https://agentmods.dev/badge/commands/obeone/claude-skills/automode-edit.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.00043 | $0.02335 |
| Opus 5 | $0.00022 | $0.01167 |
| Sonnet 5 | $0.00009 | $0.00467 |
| Haiku 4.5 | $0.00004 | $0.00233 |
Grade B, and why
automode-edit scanned grade B 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`--write-shared`, never touch `~/.claude/settings.json`, unless the How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/automode-edit <query>
Translate a natural-language request into a structured modification of
.claude/settings.local.json → autoMode, then drive the existing
six-phase apply pipeline. The agent is the interpreter; the deterministic
guards (schema validation, mistaken-pattern detection, critique gate,
hash gate, atomic write under flock) still apply.
<query> examples:
add a hard_deny rule that forbids pushing to mainallow deploys to the staging namespacethe github org is acme-corp, all repos under it are internaldrop the soft_deny entry about npm installtake ownership of the allow section (remove $defaults)restore $defaults in soft_denyrename the rule about migrations to mention the new ./scripts/migrate.sh path
Hard rules (do not violate)
- Prose, not patterns. Rules are natural-language sentences. If the
user dictates
Bash(...),Read(...),WebFetch(...), etc., refuse and explain that those belong inpermissions, not inautoMode. - Four sections only.
environment,allow,soft_deny,hard_deny. Reject any other section. Migrate legacydeny→soft_deny, dropaskwith a warning. - Never silently drop
"$defaults". If the user's request implies removing the sentinel from a section, surface the consequence (which curated baseline they lose) and require an explicit confirm. - Write target is
.claude/settings.local.jsononly. Never--write-shared, never touch~/.claude/settings.json, unless the user explicitly asks for it inside<query>and confirms again after the diff. - No bypass of the pipeline. Always go through
apply_automode.py--dry-run→ user confirm →--approved-canonical-hash. Never write the JSON file directly. - Read before edit. Re-read
.claude/settings.local.jsonright before building the proposal; do not rely on cached content from earlier in the session.
Step 1 — load current state
Resolve paths and read state with the project's own scripts:
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.
- 6d ago First seen · 230 lines · 43 tokens per session scan B 5795fcbde403
automode-edit is a command published in the GitHub repository obeone/claude-skills (3 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 2,335 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
drupal
Perform comprehensive Drupal 11 code audit and security analysis.
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
sync-to-copilot
Sync skills and instructions from Claude or Codex to GitHub Copilot CLI.