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/skills/fredchu/claude-dotfiles/automl)<a href="https://agentmods.dev/skills/fredchu/claude-dotfiles/automl"><img src="https://agentmods.dev/badge/skills/fredchu/claude-dotfiles/automl.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.00069 | $0.01508 |
| Opus 5 | $0.00034 | $0.00754 |
| Sonnet 5 | $0.00014 | $0.00302 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade B, and why
automl 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| `command == "clear"` | Call `scripts/lifecycle_commands.py::clear(state)`; on success, `rm -rf` the run directory. | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/automl v6.0
Calibrator subagent → alignment dialogue → round loop → audit → terminal lifecycle, with 6 always-on gates (iteration / wall-time / repeat-loop / budget / context / quota) via FIXED ORDER tick_gate orchestrator + RED_TEAM opt-in dispatch + multi-session safety (active_session lock, cross-session quota coordination, worktree advisory, orphan recovery) + calibrator self-improvement telemetry (run_summary.md per terminal run, weekly aggregator alerts on Discord).
Spec: docs/superpowers/specs/2026-05-06-automl-v6-design.md
Algorithm: ALGORITHM.md
Changelog: CHANGELOG.md
Shared quota gate
/automl has an always-on quota gate. Use the shared helper first so this skill
and Codex/Codex CLI share the same semantics:
/Users/fredchu/bin/agent-orch quota check --provider claude --threshold 85 --on-error fail-open --json
- exit 0 /
decision=="allow":continue the normaltick_gateloop. - exit 2 /
decision=="wait":transition lifecycle to quota-wait/paused as the run state already supports, callScheduleWakeupfor JSONresume_at, and resume from.automl/<run_id>/state.jsonafter waking. Re-run quota check before continuing. decision=="probe_failed":retry afterretry_at/retry_after_seconds; do not treat probe failure as a 5h reset.- If
agent-orchis unavailable, fall back to the legacyscripts/quota_check.pypath for compatibility.
Commands
/automl <freeform goal description> start a new run (calibrator + alignment + round loop)
/automl --spec <path/to/goal.md> start from existing goal.md (skip alignment)
/automl pause [run_id] pause an active run (release session lock)
/automl resume [run_id] resume a paused run (claim session lock)
/automl status [run_id] multi-section run status (spec §8.3 format)
/automl clear <run_id> delete a terminal run's directory
/automl list scan cwd .automl/ + per-run summary
/automl history calibrator vs actual telemetry across runs
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- ALGORITHM.md 281 B
- CHANGELOG.md 13 KB
- prompts/budget_limit.md 1.2 KB
- prompts/calibrator.md 1.4 KB
- prompts/continuation.md 1.8 KB
- prompts/red_team.md 1.1 KB
- README.md 300 B
- references/mini-brainstorm.md 1.5 KB
- references/mini-grill.md 1.5 KB
- schemas/calibrator_output.schema.json 2.5 KB
- schemas/env_json.schema.json 730 B
- schemas/goal_md.schema.yaml 1.1 KB
- schemas/red_team_output.schema.json 918 B
- schemas/round_output.schema.json 2.2 KB
- schemas/state_json.schema.json 3.4 KB
- scripts/__init__.py 0 B runs code
- scripts/alignment_dialogue.py 3.4 KB runs code
- scripts/audit_gatekeeper.py 1.9 KB runs code
- scripts/calibrator_dispatch.py 1.7 KB runs code
- scripts/cli_parser.py 4.7 KB runs code
- scripts/env_probe.py 2.1 KB runs code
- scripts/gates/__init__.py 0 B runs code
- scripts/gates/budget_gate.py 1.1 KB runs code
- scripts/gates/context_gate.py 1.2 KB runs code
- scripts/gates/iteration_gate.py 695 B runs code
- scripts/gates/quota_gate.py 3.6 KB runs code
- scripts/gates/repeat_loop_gate.py 1.1 KB runs code
- scripts/gates/wall_time_gate.py 1013 B runs code
- scripts/goal_io.py 2.0 KB runs code
- scripts/history_command.py 1.9 KB runs code
- scripts/lifecycle_commands.py 2.6 KB runs code
- scripts/lifecycle_fsm.py 1.5 KB runs code
- scripts/list_command.py 1.5 KB runs code
- scripts/orchestrator.py 8.9 KB runs code
- scripts/orphan_recovery.py 2.0 KB runs code
- scripts/quota_coordinator.py 866 B runs code
- scripts/red_team_dispatch.py 2.1 KB runs code
- scripts/round_dispatch.py 2.2 KB runs code
- scripts/run_summary_io.py 518 B runs code
- scripts/run_summary.py 4.2 KB runs code
- scripts/schema_validators.py 2.5 KB runs code
- scripts/session_lock.py 1.6 KB runs code
- scripts/spec_bypass.py 2.4 KB runs code
- scripts/state_io.py 3.2 KB runs code
- scripts/status_renderer.py 3.9 KB runs code
- scripts/tick_gate.py 3.2 KB runs code
- scripts/worktree_advisory.py 4.6 KB runs code
- tests/conftest.py 180 B runs code
- tests/e2e/__init__.py 0 B runs code
- tests/e2e/conftest.py 2.1 KB runs code
- tests/e2e/test_concurrent_cwd_refused.py 1.8 KB runs code
- tests/e2e/test_cross_session_takeover.py 2.7 KB runs code
- tests/e2e/test_gate_budget_limit_wrapup.py 1.6 KB runs code
- tests/e2e/test_gate_quota_pause_resume.py 1.7 KB runs code
- tests/e2e/test_gate_repeat_loop_aborts.py 1.8 KB runs code
- tests/e2e/test_happy_path.py 3.5 KB runs code
- tests/e2e/test_orphan_autonomous_takeover.py 2.5 KB runs code
- tests/e2e/test_pause_resume_cycle.py 1.9 KB runs code
- tests/e2e/test_terminal_writes_run_summary.py 2.2 KB runs code
- tests/fixtures/sample_calibrator_outputs/invalid_no_criteria.json 491 B
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 · 100 lines · 69 tokens per session scan B 7ddf6353ad47
automl is a skill published in the GitHub repository fredchu/claude-dotfiles (2 stars, last pushed 23d ago), licensed MIT. It adds 69 tokens to every session and 1,508 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B 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 skills, from other repositories
setup-matt-pocock-skills
为本仓库配置工程技能——设置其 issue tracker、分诊标签词汇表和领域文档布局。首次使用其他工程技能前运行一次。.
triage
将 issue 和外部 PR 推过一组分诊角色的状态机——分类、验证、必要时盘问,并写出 agent 就绪的任务简报。.
scaffold-exercises
创建包含 section、problem、solution 和 explainer 的练习目录结构,且能通过 lint 检查。当用户想要搭建练习框架、创建练习模板或设置新的课程章节时使用。.
migrate-to-shoehorn
将测试文件从 as 类型断言迁移到 @total-typescript/shoehorn。当用户提到 shoehorn、想要在测试中替换 as、或需要部分测试数据时使用。.
setup-pre-commit
在当前仓库中设置 Husky pre-commit 钩子,集成 lint-staged(Prettier)、类型检查和测试。当用户想要添加 pre-commit 钩子、设置 Husky、配置 lint-staged、或添加提交时的格式化/类型检查/测试时使用。.
grilling
对用户的计划、决策或想法进行层层盘问。当用户想要压力测试自己的思考,或使用任何 'grill' 触发短语时使用。.