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 skills/easyinplay/harnessed/autonpx skills add easyinplay/harnessed --skill autogit clone --depth 1 https://github.com/easyinplay/harnessedWrote 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/easyinplay/harnessed/auto)<a href="https://agentmods.dev/skills/easyinplay/harnessed/auto"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/auto.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.00221 | $0.03649 |
| Opus 5 | $0.00111 | $0.01825 |
| Sonnet 5 | $0.00044 | $0.00730 |
| Haiku 4.5 | $0.00022 | $0.00365 |
Grade A, and why
auto 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 3d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auto super-master orchestrator (v3.2.0 enhanced)
Overview
v3.2.0 NEW — 6-stage cadence (research conditional → discuss → plan → task → verify → retro
mandatory), sister 4 stage-master /discuss /plan /task /verify 独立 invoke 仍 work;
/auto 是 opt-in 一行命令 chain。
| order | sub | gate ref | mode | when fires |
|---|---|---|---|---|
| 0 | research |
judgments.stage-routing.auto-research-unclear.fires |
serial | user_understanding_unclear == true (Phase 0.5 prompt n) |
| 1 | discuss |
(unconditional — 4-stage chain 起点) | serial | always |
| 2 | plan |
(unconditional — stage 2) | serial | always |
| 3 | task |
(unconditional — stage 3) | serial | always |
| 4 | verify |
(unconditional — stage 4 收尾) | serial | always |
| 5 | retro |
(unconditional — auto mode mandatory) | serial | always |
Engine runtime spawns 6 sub workflow.yaml via runMasterOrchestrator per
T3.5.W0.1 — recursive 一层抽象 (super-master → stage-master OR standalone → sub-workflow):
- top-level invoke
/auto→ loadworkflows/auto/workflow.yaml→ runAutoPreFlight hook - pre-flight Phase 0:
assessComplexity(taskDescription)→ small/medium auto continue; large → prompt user 切--staged(y) OR abort 建议手动 (n) - pre-flight Phase 0.5:
promptUserUnderstanding()→ y skip research; n setuser_understanding_unclear = true进 ctx → research gate fires - spawn order 0:
workflows/research/workflow.yaml(if gate fires) - spawn order 1-4: 4 stage-master
workflows/<sub>/auto/workflow.yaml - spawn order 5:
workflows/retro/workflow.yaml(mandatory unconditional)
K8 ctx single snapshot:auto top-level invoke 1 snapshot, pass to all 6 spawn (sister Phase 3.5 W0.1 pattern verbatim, 1 snapshot per top-level invoke 跨整个 cycle)。
Default behavior
- Pre-flight gates: complexity assessment + understanding check (interactive prompts)
- Continuous chain: 6 stage 一行命令跑完, 中间不停
- Fail-fast: 任一 stage fail 立即停,
harnessed resume续 - New-project bootstrap:
.planning/ROADMAP.mdmissing → stage ① runs/gsd-new-project(when available) or creates the minimal ROADMAP/STATE/REQUIREMENTS skeleton first - Context 自动传递: planning-with-files
.planning/phases/<NN>-<slug>/喂下 stage - Retro mandatory: auto mode hands-off scenario,末尾强制
/retro总结 (无 opt-out flag) - 沿用 sister planning-with-files /plan 持久化 cadence
What ships with it
2 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.
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.
- 3d ago First seen · 156 lines · 221 tokens per session scan A e36b60cc88ae
auto is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 221 tokens to every session and 3,649 once invoked, about $0.0011 per session on Opus 5. 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 skills, from other repositories
harness
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/ /adr- - .md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural…
architecture
Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads existing tech-spec as input. Use when: designing system architecture, documenting component interactions, creating architecture docs, producing 3-architecture.md.…
doc-review
Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate.