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.
npx agentmods add skills/rossoctl/examples/orchestrate-replicatenpx skills add rossoctl/examples --skill orchestrate-replicategit clone --depth 1 https://github.com/rossoctl/examplesWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00028 | $0.01000 |
| Opus 5 | $0.00014 | $0.00500 |
| Sonnet 5 | $0.00006 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
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 2d 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.
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:precommitandorchestrate:cicomplete (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:
- Remove source-specific references — strip rossoctl-specific paths or assumptions that don't apply
- Verify frontmatter — every
name:field must match its directory name - Update Related Skills — only reference skills that exist in the copied set
- 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 |
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.
- 2d ago First seen · 126 lines · 28 tokens per session scan A c1086a3c2465
orchestrate:replicate is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,000 once invoked, about $0.0001 per session on Opus 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.
Other skills, from other repositories
importing-a-codebase
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.