Operator Approval Loop
affaan-m/ECC
Operator approval contract with internal filing notices for agent-drafted outbound messages, hashed drafts, epoch-keyed decisions, durable delivery claims and receipts, and a pre-draft baseline gate.
A skill your agent uses when choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow.
MITAuto-check passed
Install Mode Selection
$ npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mtarcure/claude-vibe-squad mode-selection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mode-selection .claude/skills/mode-selection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mode-selection" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selection into .claude/skills/mode-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mode-selection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mtarcure/claude-vibe-squad mode-selection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mode-selection .agents/skills/mode-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mode-selection" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selection into .agents/skills/mode-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mode-selection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mtarcure/claude-vibe-squad mode-selection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mode-selection .cursor/skills/mode-selection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mode-selection" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selection into .cursor/skills/mode-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mode-selection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mtarcure/claude-vibe-squad.git --path .claude/skills/mode-selection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mtarcure/claude-vibe-squad mode-selection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mode-selection .gemini/skills/mode-selection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mode-selection" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selection into .gemini/skills/mode-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mode-selection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mtarcure/claude-vibe-squad mode-selectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mode-selection .github/skills/mode-selection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mode-selection" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selection into .github/skills/mode-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mode-selection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mtarcure/claude-vibe-squad mode-selection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mode-selection .opencode/skills/mode-selection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mode-selection" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.claude/skills/mode-selection into .opencode/skills/mode-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mode-selection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mode-selection- GitHub stars
- 163
- Token cost
- ~961 tokens
- SKILL.md length
- 476 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow.
- Choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow
- SKILL.md covers Name the mode and get approval…, Both dispatch paths preserve…, Verify the mode that LANDED,… and The mode changes the contract,…
- Calls python3
What it does
Mode Selection is an agent skill from mtarcure/claude-vibe-squad. Use when choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow. Not for constructing fields or reviewer routing.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Multi-model AI orchestration where behaviour is Markdown, not code. One coordinator routes scoped task packets to 71 role-based specialists across 5 model families (Codex /… The licence is MIT.
When your agent uses it
- Choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow
Example prompts
- “/mode-selection”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 7bd69f8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mode Selection loads about 961 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 476 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mtarcure/claude-vibe-squad at commit 7bd69f8, republished under its MIT licence (© mtarcure). 476 words, ~961 tokens.
Download SKILL.mdSave it as
.claude/skills/mode-selection/SKILL.md (or your agent's skills folder).- name
- mode-selection
- description
- Use when choosing the operator-approved `mode` (`project` versus `bounty`) before launch—approval of the work does not approve that workflow. Not for constructing fields or reviewer routing.
- audience
- chrono
Mode Selection
House procedure for choosing a dispatch mode before authoring the packet. The mode is a separate operator decision from the work itself, and the wrong mode silently changes the wall, the verification contract, and the gates a lane runs under. Verify every claim here against the current scripts — do not trust this doc over the code.
Name the mode and get approval — it is its own consent
chrono/CLAUDE.mdDispatch step 1 requires opening the chosen file undershared/modes/, stating which mode the work will run under, and waiting for the operator to agree. Hard Rule 1 forbids a mode starting without explicit consent.- Approving the work is not approving the mode. A convenience wrapper's silent default sent most of a campaign's lanes under a mode nobody chose — without telling the operator. Say the mode word out loud; never infer it from "yes, go".
Both dispatch paths preserve an explicit choice
- Generated packets use
scripts/send-task.sh ... --mode project|bounty. The wrapper rejects an omitted or invalid value, writes the exact choice into frontmatter, and never supplies a default. - Prepared packets carry
mode: project|bountyin frontmatter and dispatch withbin/send-task.sh <packet-file>, which carries the packet's ownmodeinto the compiled contract (MODE_VALUE->"mode"). - The wrapper survives because it still assembles standard frontmatter, resolves lanes and review metadata, and routes through the hardened dispatcher. Retire it only if those conveniences move elsewhere; do not retain or reintroduce a mode default as its reason to exist.
Show full SKILL.md (252 more words)Show less
Verify the mode that LANDED, never the one you intended
- The dispatch context carries the landed mode as a real field. Read it from the exact attempt you
dispatched, never from a glob — attempt ids are UUIDs, so glob order is not chronological and
head -1can hand you a previous attempt's mode after a retry:bash python3 -c 'import json,sys; a=json.load(open(sys.argv[1]))["authority"]; \ p=a.get("mode_profile"); m=(a.get("memory_context") or {}).get("mode"); \ print(p if p==m else f"MISMATCH profile={p} memory={m}")' <context_path>mode_profileandmemory_context.modemust agree; if they disagree, stop — do not pick one. - A wrapper
--dry-runechoesPacket mode: <mode>and derives that mode's contract. It proves the generated packet's choice but not a landed attempt; a green prepared-packet dry-run likewise does not replace the exact-attempt check. - If the landed mode differs from what the operator approved, stop and say so before the lane works.
The mode changes the contract, not just the wall
- Walls come from
timeout_budget_for_mode()indispatch_context_builder.py: a flat 2700s forproject, 3600s forbounty. Scope to the emitted number; do not infer it from a ratio. verification_contract.pysets a different contract per mode.projectrequiresproject_tests/recipient_contractand mandatory recall+record.bountyswaps inscope_gate/no_self_inflicted/poc_reproduction, an exact target allowlist, forbids submission-attempted, and makes recall OPTIONAL (a cold lane cannot recall without inheriting other runs' conclusions).projectandbountyboth carry aplan_review_policywithanti_affinity: author_family— an independent-family plan check is part of the contract. That is the controller's plan review and is separate from the deliverable's ownreview_model; aprojectpacket withreview_model: nonestill launches.
© mtarcure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/mode-selection of mtarcure/claude-vibe-squad.
Open the folder on GitHubat commit 7bd69f8
Compare with similar skills
Mode Selection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mode Selection this skillmtarcure/claude-vibe-squad | 163 | — | ~961 | Automated safety check: Pass | MIT | |
| Operator Approval Loopaffaan-m/ECC | 275k | — | ~3.3k | Automated safety check: Pass | MIT | |
| It Operationsdavila7/claude-code-templates | 32k | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Security Bounty Hunteraffaan-m/ECC | 275k | 2 repos | ~907 | Automated safety check: Pass | MIT | |
| Bug Bountysickn33/agentic-awesome-skills | 47k | 1 repos | ~5k | Automated safety check: Notes | MIT | |
| Business Operations Skillsalirezarezvani/claude-skills | 28k | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
It Operations
davila7/claude-code-templates
Manages IT infrastructure, monitoring, incident response, and service reliability.
Security Bounty Hunter
affaan-m/ECC
Hunt for exploitable, bounty-worthy security issues in repositories.
Bug Bounty
sickn33/agentic-awesome-skills
Complete bug bounty workflow
Business Operations Skills
alirezarezvani/claude-skills
A skill your agent uses when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook authoring…
Kubernetes Operator
alirezarezvani/claude-skills
A skill your agent uses when building a Kubernetes Operator — custom controllers that reconcile CRD state.
More from mtarcure/claude-vibe-squad
All 17 skills in this repoSystematic Attacking
mtarcure/claude-vibe-squad
A skill your agent uses for ALL authorized offensive-security / bug-bounty work — the single method to find, chain, prove, dedup, and package the highest-value (High/Critical) findings across every…
Blind Rediscovery
mtarcure/claude-vibe-squad
Operational checklist + helper for blind-rediscovery fan-out work.
Chain Construct Smart Contract
mtarcure/claude-vibe-squad
A skill your agent uses when you have a confirmed on-chain vulnerability hypothesis and must demonstrate it with a passing proof-of-concept — author an attacker contract or crafted instruction…
Compact Now
mtarcure/claude-vibe-squad
Operator-triggered proactive compaction — Chrono externalizes load-bearing state (active decisions, open tasks, next action) to a snapshot + a durable Vault learning note before invoking Claude…
Agent Prompt Engineering
mtarcure/claude-vibe-squad
A skill your agent uses when building or revising the system prompt for a product agent and you need an eval-backed boundary, tool-use, grounding, and output contract.
Defi Invariant Check
mtarcure/claude-vibe-squad
A skill your agent uses when the audit target is a DeFi protocol — AMM, lending market, yield vault, stablecoin, or perps — and you must author the economic properties generic campaigns miss, such…
Questions about Mode Selection
What does Mode Selection do?
A skill your agent uses when choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow. Mode Selection is an agent skill from mtarcure/claude-vibe-squad. Use when choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow.
When should I use Mode Selection?
Mode Selection fits situations like: choosing the operator-approved mode (project versus bounty) before launch—approval of the work does not approve that workflow.
How do I install Mode Selection in Claude Code?
Run `npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a claude-code`. Or copy the skill folder (.claude/skills/mode-selection in mtarcure/claude-vibe-squad) into .claude/skills/mode-selection in your project. Claude Code loads it when a task matches its description.
How do I install Mode Selection in Codex?
Run `npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a codex`. Or copy the skill folder (.claude/skills/mode-selection in mtarcure/claude-vibe-squad) into .agents/skills/mode-selection in your project. Codex loads it when a task matches its description.
Can I use Mode Selection in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mtarcure/claude-vibe-squad --skill mode-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mode-selection, .gemini/skills/mode-selection, .github/skills/mode-selection and .opencode/skills/mode-selection in your project.
What does Mode Selection need to run?
Going by SKILL.md and its folder, Mode Selection needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Mode Selection access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mode Selection safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mode Selection use?
Mode Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mode Selection use?
About 961 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mode Selection?
Skills that share tags, products or a category with Mode Selection: Operator Approval Loop (affaan-m/ECC, 275k stars), It Operations (davila7/claude-code-templates, 32k stars), Security Bounty Hunter (affaan-m/ECC, 275k stars) and Bug Bounty (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mode Selection?
mtarcure (a GitHub user) maintains it in mtarcure/claude-vibe-squad, which has 163 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 21, 2026.
Source: mtarcure/claude-vibe-squad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.