install

install is a skill for Claude Code from qGolem/orc. It costs 25 tokens per session (7,925 once invoked), scanned C, original, MIT.

An interactive setup wizard for the orc plugin, a collection of Claude Code commands for planning and code review. It checks the installation and guides you through configuration choices.

In plain words
What is it for?
Use it to install or verify the orc plugin, configure script permissions and runtime tools, inspect draw.io and MCP setup, and take a guided tour of its commands.
Why use it?
It helps identify missing Claude Code versions, permissions, scripts, hooks, and related setup before you use the plugin. It also explains which parts are already loaded and what commands are available.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

Part of the orc plugin — 28 skills, 27 agents shipped together

Good fit Use it to install or verify the orc plugin, configure script permissions and runtime tools, inspect draw.io and MCP setup, and take a guided tour of its commands.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/qgolem/orc/install
View source ↗ qGolem/orc
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 qGolem/orc --skill install
Clone the repo
git clone --depth 1 https://github.com/qGolem/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 28 skills, 27 agents.

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 install

README.md
[![agentmods](https://agentmods.dev/badge/skills/qgolem/orc/install/github.svg)](https://agentmods.dev/skills/qgolem/orc/install)
Your own site
<a href="https://agentmods.dev/skills/qgolem/orc/install"><img src="https://agentmods.dev/badge/skills/qgolem/orc/install/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 install

Your own site · 80×15
<a href="https://agentmods.dev/skills/qgolem/orc/install"><img src="https://agentmods.dev/badge/skills/qgolem/orc/install.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,925 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00025 $0.07925
Opus 5.5 $0.00010 $0.03170
Sonnet 5.5 $0.00005 $0.01585
Haiku 4.5 $0.00003 $0.00792

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

Security

Grade C, and why

install scanned grade C with 2 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

find ~/.claude/plugins -path "*/install/templates/deps" -type d 2>/dev/null | head -1

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

find skills/ .claude/skills/ -name "*.sh" -type f 2>/dev/null
skills/install/SKILL.md · 859 lines

How it starts

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

Install

Interactive setup wizard for the orc plugin. Uses AskUserQuestion for every decision point.

Process

Step 1: Welcome and Verify Claude Code

claude --version 2>/dev/null || echo "NOT_FOUND"

If NOT_FOUND: tell user to install Claude Code first, then re-run /orc:install.

Otherwise extract version. If < 1.0.33, warn that some features may not work.

Display welcome:

Welcome to orc — orchestrated planning and code review for Claude Code.

Step 2: Check plugin status

The fact that this skill is running means the plugin is loaded. Confirm this.

Determine context:

ls skills/install/SKILL.md 2>/dev/null && echo "IS_PLUGIN_REPO" || echo "IS_CONSUMER"

If IS_PLUGIN_REPO: Note they can load from any project with claude --plugin-dir /path/to/this/repo.

If IS_CONSUMER: Plugin is installed correctly.

Step 3: Script permissions and runtime setup

Discover all scripts and hooks that need execution access:

find skills/ .claude/skills/ -name "*.sh" -type f 2>/dev/null
ls .claude/hooks/index.ts 2>/dev/null && echo "HAS_HOOKS" || true

For each script found, present an AskUserQuestion with:

  1. A description of what the script does
  2. An ASCII diagram of its execution flow
  3. A choice to grant execute permission or skip

Important: Check current permissions first with ls -la <path>. If already executable, note this and skip the question.


Script: skills/half-clone/scripts/half-clone-conversation.sh

What it does: Clones the later half of a Claude Code conversation into a new session, discarding earlier context to free tokens. Used by /orc:half-clone.

Present this to the user:

<AskUserQuestion>
  <Question
    question="Grant execute permission to half-clone-conversation.sh?"
    header="half-clone"
    multiSelect="false"
    options='[
      {"label": "Grant (Recommended)",
       "description": "chmod +x — required for /orc:half-clone to work",
       "preview": "half-clone-conversation.sh (575 lines)\n\nUsed by: /orc:half-clone\nRuntime: bash 3.2+ (macOS/Linux)\nInput:   session-id, project-path\nOutput:  new .jsonl conversation file\n\n┌─────────────────────────────────────┐\n│  /orc:half-clone                    │\n│  └─ calls half-clone-conversation.sh│\n└──────────────┬──────────────────────┘\n               │\n               ▼\n┌──────────────────────────────────┐\n│ 1. Find conversation .jsonl      │\n│    ~/.claude/projects/<dir>/     │\n│    └─ <session-id>.jsonl         │\n└──────────────┬───────────────────┘\n               │\n               ▼\n┌──────────────────────────────────┐\n│ 2. Count clean user messages     │\n│    Filter: type=user, skip meta  │\n│    Calculate halfway point       │\n└──────────────┬───────────────────┘\n               │\n               ▼\n┌──────────────────────────────────┐\n│ 3. Generate new session UUID     │\n│    Pre-generate UUIDs for awk    │\n│    (batch, not per-line)         │\n└──────────────┬───────────────────┘\n               │\n               ▼\n┌──────────────────────────────────┐\n│ 4. Single-pass awk transform     │\n│    ├─ Skip first N lines         │\n│    ├─ Remap session/msg UUIDs    │\n│    ├─ Strip thinking blocks      │\n│    ├─ Halve token counts         │\n│    └─ Tag first kept message     │\n└──────────────┬───────────────────┘\n               │\n               ▼\n┌──────────────────────────────────┐\n│ 5. Write new .jsonl + history    │\n│    ~/.claude/projects/<dir>/     │\n│    └─ <new-session>.jsonl        │\n│    ~/.claude/history.jsonl       │\n│    └─ append entry               │\n└──────────────────────────────────┘\n\nSafe: reads original, writes new file.\nNo destructive operations."},
      {"label": "Skip",
       "description": "Don't grant — /orc:half-clone won't work until you do"}
    ]'
  />
</AskUserQuestion>

Read the full file on GitHub · 859 lines

Files

What ships with it

6 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.

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 · 859 lines · 25 tokens per session scan C 538c43a102f5

Subscribe to this mod's changes

install is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 7,925 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

new-skill

Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…

hyhmrright/brooks-lint · 145 tokens

llm-friendly-context

Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.

shinpr/claude-code-workflows · 52 tokens

apex-review

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

tonone-ai/tonone · 46 tokens

prompt-tuning

Tune a prompt, or anything whose quality is measured by non-deterministic model output, without chasing noise - a noise baseline before the first edit, medians over repeated runs, enforcement AFTER generation rather than in the wording. Use when iterating on prompts or model-judged output.

jjanczur/tyran · 58 tokens

brainstorm

Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.

greglas75/zuvo · 56 tokens

performance-audit

Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…

greglas75/zuvo · 90 tokens