orca-confirm

orca-confirm is a skill for Claude Code, Codex from adilkalam/orca. It costs 14 tokens per session (1,304 once invoked), scanned A, original, MIT.

A procedure for confirming which group of coding agents should handle a request, with an automatic mode for cases where no answer is returned.

In plain words
What is it for?
Use it when assigning architecture, implementation, specialist, and verification roles to an agent team.
Why use it?
It helps coordinate agent selection without repeatedly asking for confirmation or leaving the workflow unclear.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool.

Good fit Use it when assigning architecture, implementation, specialist, and verification roles to an agent team.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adilkalam/orca/orca-confirm
Install

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.

Any agent
npx skills add adilkalam/orca --skill orca-confirm
Clone the repo
git clone --depth 1 https://github.com/adilkalam/orca

Made for: Claude Code, Codex.

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.

agentmods badge for orca-confirm

README.md
[![agentmods](https://agentmods.dev/badge/skills/adilkalam/orca/orca-confirm/github.svg)](https://agentmods.dev/skills/adilkalam/orca/orca-confirm)
Your own site
<a href="https://agentmods.dev/skills/adilkalam/orca/orca-confirm"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/orca-confirm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for orca-confirm

Your own site · 80×15
<a href="https://agentmods.dev/skills/adilkalam/orca/orca-confirm"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/orca-confirm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.01304
Opus 5.5 $0.00006 $0.00522
Sonnet 5.5 $0.00003 $0.00261
Haiku 4.5 $0.00001 $0.00130

Measured 1mo ago against content hash eddad6ac09b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orca-confirm 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 1mo 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.

skills/orca-confirm/SKILL.md · 232 lines

How it starts

The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orca Team Confirmation Skill

Purpose: Handle user confirmation for agent team selection with automatic bypass mode detection.

Input: User's request is implicitly available. You receive the proposed team and project type as arguments.


Critical Rules (Read First)

  1. Ask for confirmation ONCE using AskUserQuestion
  2. Check response structure immediately after receiving it
  3. If response.answers is empty → BYPASS MODE → Return immediately
  4. NEVER retry AskUserQuestion if first attempt returned blank
  5. Return a structured result that main /orca can parse

Implementation

Step 1: Present Proposed Team (VISIBLE OUTPUT - NOT IN TOOL CALL)

CRITICAL: This must be VISIBLE MARKDOWN OUTPUT, not inside AskUserQuestion.

Output this as regular text so the user can see it:

## Proposed Pipeline

**Request:** [task description]
**Domain:** [PROJECT_TYPE]
**Complexity:** [simple/medium/complex]

### Agent Team
| Role | Agent |
|------|-------|
| Coordination | [grand-architect] |
| Architecture | [architect] |
| Implementation | [builder] |
| Specialists | [list them] |
| Gates | [gate agents] |
| Verification | [verification agent] |

### Files Likely Affected
- [from ContextBundle]

### Risks/Notes
- [any identified]

This output MUST appear BEFORE you call AskUserQuestion.

Step 2: Ask for Confirmation (ONCE ONLY - SIMPLE QUESTION)

Use AskUserQuestion with these exact options:

Question: "Proceed with this team?"
Options:
1. "Yes, proceed" → Proceed with proposed team
2. "Modify team" → Ask user what to change

Step 3: Check Response Structure

Immediately after AskUserQuestion returns, check the response:

# Pseudo-code for what you MUST check:
if response is None or response.get("answers") is None or len(response.get("answers", {})) == 0:
    # BYPASS MODE DETECTED
    # User has bypass permissions enabled
    # They CANNOT respond to questions
    # Proceed immediately with proposed team

    Output:
    " Proceeding with proposed team (bypass mode detected - confirmation unavailable)

    Proposed Team: [list team]

    You can interrupt if you need changes."

    # Return to /orca with: BYPASS|original_team

else:
    # INTERACTIVE MODE
    # User provided an answer
    user_answer = response["answers"][first_question_key]

    if user_answer == "Yes, proceed":
        Output: " Team confirmed"
        # Return to /orca with: CONFIRMED|original_team

    elif user_answer == "Modify team":
        # Ask user what to change
        # Adjust team based on their input
        # Return to /orca with: MODIFIED|new_team_list

Read the full file on GitHub · 232 lines

Changes

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.

  1. 1mo ago First seen · 232 lines · 14 tokens per session scan A eddad6ac09b2

Subscribe to this mod's changes

orca-confirm is a skill published in the GitHub repository adilkalam/orca (2 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,304 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens