examples: Skill for Claude Code

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

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

A workflow that copies orchestration skills into another repository and adapts its references and instructions. A repository is a project’s version-controlled folder.

In plain words
What is it for?
Completing the final orchestration phase after pre-commit and continuous-integration work, where continuous integration automatically checks changes.
Why use it?
It makes the target repository able to coordinate related repositories on its own, while checking the copied skills before creating a branch and pull request.

Skill for Claude Code

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

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:replicate/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:replicate

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate-replicate"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate-replicate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,000 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.00028 $0.01000
Opus 5.5 $0.00011 $0.00400
Sonnet 5.5 $0.00006 $0.00200
Haiku 4.5 $0.00003 $0.00100

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

Security

Grade A, and why

orchestrate:replicate 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:replicate/SKILL.md · 126 lines

How it starts

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

flowchart TD
    START(["/orchestrate:replicate"]) --> COPY["Copy orchestrate skills"]:::orch
    COPY --> ADAPT["Adapt references"]:::orch
    ADAPT --> UPDATE["Update target CLAUDE.md"]:::orch
    UPDATE --> VALIDATE["Validate skills"]:::orch
    VALIDATE --> BRANCH["Create branch"]:::orch
    BRANCH --> PR["Commit + open PR"]:::orch
    PR --> DONE([Target self-sufficient])

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

Follow this diagram as the workflow.

Orchestrate: Replicate

The final orchestration phase. Copies orchestrate skills into the target repo, making it fully self-sufficient. This is Phase 6.

When to Use

  • Final phase of orchestration
  • After at least precommit + CI phases are complete
  • When you want the target repo to orchestrate its own related repos

Prerequisites

  • orchestrate:precommit and orchestrate:ci complete (at minimum)
  • Target repo has .claude/ directory

What Gets Copied

Skill Purpose
orchestrate/ Router — entry point
orchestrate:scan/ Assess repos
orchestrate:plan/ Create phased plans
orchestrate:precommit/ Add pre-commit hooks
orchestrate:ci/ Add CI workflows
orchestrate:tests/ Add test infrastructure
orchestrate:security/ Add security hardening
orchestrate:replicate/ This skill (self!)
skills:scan/ Discover skills in a repo
skills:write/ Author new skills
skills:validate/ Validate skill structure

Adaptation Steps

After copying, adapt the skills:

  1. Remove source-specific references — strip rossoctl-specific paths or assumptions that don't apply
  2. Verify frontmatter — every name: field must match its directory name
  3. Update Related Skills — only reference skills that exist in the copied set
  4. Preserve generality — skills should work in any repo context

Update Target CLAUDE.md

Add an orchestration section:

## Orchestration

This repo includes orchestrate skills for enhancing related repos:

| Skill | Description |
|-------|-------------|
| `orchestrate` | Run `/orchestrate <repo-path>` to start |
| `orchestrate:scan` | Assess repo structure and gaps |
| `orchestrate:plan` | Create phased enhancement plan |
| `orchestrate:replicate` | Bootstrap skills into target |

Read the full file on GitHub · 126 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 · 126 lines · 28 tokens per session scan A c1086a3c2465

Subscribe to this mod's changes

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