examples: Skill for Claude Code

.claude/skills/orchestrate:plan/SKILL.md

orchestrate:plan is a skill for Claude Code from rossoctl/examples. It costs 26 tokens per session (1,138 once invoked), scanned A, original, Apache-2.0.

A planning workflow for turning a repository review into a staged list of improvements. A repository is the project's code and related files.

In plain words
What is it for?
Use it to review a scan report, discuss priorities, choose improvement phases, break work into tasks, and write a plan for separate pull requests.
Why use it?
It helps decide which improvements matter, how to group them, and what order to tackle them in before code changes begin.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

This is rossoctl/examples's own configuration. It tells Claude Code how to work on examples itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything examples configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rossoctl/examples. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rossoctl/examples/main/.claude/skills/orchestrate:plan/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rossoctl/examples

Made for: Claude Code.

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 orchestrate:plan

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate-plan"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,138 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00026 $0.01138
Opus 5.5 $0.00010 $0.00455
Sonnet 5.5 $0.00005 $0.00228
Haiku 4.5 $0.00003 $0.00114

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

Security

Grade A, and why

orchestrate:plan 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.

.claude/skills/orchestrate:plan/SKILL.md · 149 lines

How it starts

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

flowchart TD
    START(["/orchestrate:plan"]) --> READ["Read scan report"]:::orch
    READ --> PRESENT["Present findings"]:::orch
    PRESENT --> BRAINSTORM["Brainstorm with developer"]:::orch
    BRAINSTORM --> SELECT["Select applicable phases"]:::orch
    SELECT --> SIZE["Size PRs (600-700 lines)"]:::orch
    SIZE --> WRITE["Write plan document"]:::orch
    WRITE --> DONE([Plan complete])

    classDef orch fill:#FF9800,stroke:#333,color:white

Follow this diagram as the workflow.

Orchestrate: Plan

Take the scan report and turn it into a concrete phased enhancement plan. This is Phase 1 — interactive brainstorming with the developer, no PRs.

When to Use

  • After orchestrate:scan has produced a scan report
  • Before starting any PR-producing phase

Prerequisites

Scan report must exist:

cat /tmp/rossoctl/orchestrate/<target>/scan-report.md

Planning Process

1. Read the scan report

Review the Gap Summary and Recommended Phases sections.

2. Present findings to developer

Summarize the key gaps in plain language. Use AskUserQuestion to confirm understanding and gather context about the repo's priorities.

3. Brainstorm which phases apply

Not all repos need all phases. Use AskUserQuestion to decide:

Gap Found Phase Default
No pre-commit config orchestrate:precommit Always (foundation)
No/incomplete CI workflows or security scanning orchestrate:ci Yes if missing
No/few tests (<5 test files) orchestrate:tests Yes if low coverage
No CODEOWNERS/SECURITY.md/LICENSE orchestrate:security Recommended
No .claude/skills/ directory orchestrate:replicate Always (last phase)

4. Determine phase order

Default order: precommit → tests → ci → security → replicate

Tests come before CI (so CI can run them) and before security (so code refactoring for security fixes has test coverage as a safety net). Pre-commit is always first (it validates subsequent PRs). Replicate is always last.

Read the full file on GitHub · 149 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 · 149 lines · 26 tokens per session scan A 604d10973f2f

Subscribe to this mod's changes

orchestrate:plan is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 1,138 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-08-30.