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.
curl -O https://raw.githubusercontent.com/rossoctl/examples/main/.claude/skills/orchestrate/SKILL.mdgit clone --depth 1 https://github.com/rossoctl/examplesWrote 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.
[](https://agentmods.dev/skills/rossoctl/examples/orchestrate)<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate/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.
<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00026 | $0.01688 |
| Opus 5.5 | $0.00010 | $0.00675 |
| Sonnet 5.5 | $0.00005 | $0.00338 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
orchestrate 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flowchart TD
START(["/orchestrate"]) --> HAS_SCAN{Has scan report?}
HAS_SCAN -->|No| SCAN["orchestrate:scan"]:::orch
SCAN --> PLAN["orchestrate:plan"]:::orch
HAS_SCAN -->|Yes| HAS_PLAN{Has plan?}
HAS_PLAN -->|No| PLAN
HAS_PLAN -->|Yes| NEXT_PHASE{Next phase?}
NEXT_PHASE -->|Phase 2| PRECOMMIT["orchestrate:precommit<br/>PR #1"]:::orch
NEXT_PHASE -->|Phase 3| TESTS["orchestrate:tests<br/>PR #2"]:::orch
NEXT_PHASE -->|Phase 4| CI["orchestrate:ci<br/>PR #3"]:::orch
NEXT_PHASE -->|Phase 5| SECURITY["orchestrate:security<br/>PR #4"]:::orch
NEXT_PHASE -->|Phase 6| REPLICATE["orchestrate:replicate<br/>PR #5"]:::orch
NEXT_PHASE -->|Phase 7| REVIEW["orchestrate:review"]:::orch
PRECOMMIT --> TESTS
TESTS --> CI
CI --> SECURITY
SECURITY --> REPLICATE
REPLICATE --> REVIEW
REVIEW --> DONE([All phases complete])
classDef orch fill:#FF9800,stroke:#333,color:white
classDef check fill:#FFC107,stroke:#333,color:black
class HAS_SCAN,HAS_PLAN,NEXT_PHASE check
Follow this diagram as the workflow.
Orchestrate Skills
Enhance any repository with CI, tests, skills, and security through a series of phased PRs. Each phase produces a focused, reviewable PR of 600-700 lines.
Entry Point Routing
When /orchestrate is invoked, determine the action:
What was provided?
|
+-- /orchestrate <repo-path>
| New target. Clone or locate the repo, then start from scan.
| Example: /orchestrate .repos/my-service
|
+-- /orchestrate <phase>
| Jump to a specific phase. Requires scan + plan to already exist.
| Example: /orchestrate ci
|
+-- /orchestrate status
Show current orchestration state for all tracked targets.
Route logic
/orchestrate <repo-path>-- If the path points to a git repository, derive the target name from the directory basename. Check/tmp/rossoctl/orchestrate/<target>/for existing state. If no scan report exists, invokeorchestrate:scan. If scan exists but no plan, invokeorchestrate:plan. If both exist, determine the next incomplete phase and invoke it.
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.
- 1mo ago First seen · 150 lines · 26 tokens per session scan A 62c23bfa1acb
orchestrate 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,688 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.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…