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 skills add LucasSantana-Dev/sharekit --skill orchestrategit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/orchestrate)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/orchestrate"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/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/lucassantana-dev/sharekit/orchestrate"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00052 | $0.00885 |
| Opus 5.5 | $0.00021 | $0.00354 |
| Sonnet 5.5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orchestrate
Use for larger delivery flows and multi-agent coordination.
Use When
- The task is large enough that parallel work will save time or add confidence.
- Independent workstreams can be defined with clear inputs, outputs, and ownership.
- One lead agent can own synthesis, integration, and final verification.
- Work spans multiple repos, skill chains, or requires worktree separation.
Do Not Use When
- The task is small, tightly coupled, or faster to complete in one session.
- Multiple agents would fight over the same files or the same mutable context.
- The user wants one narrow implementation rather than orchestration.
Core Responsibilities
- Decide whether work should be serial, parallel, or worktree-split
- Choose the controlling plan
- Keep one source of truth for current state
- Ensure each branch of work converges cleanly
- Plan and run multi-agent work without losing integration quality
Inputs / Prereqs
- The goal, success criteria, and integration owner.
- Candidate workstreams and the dependencies between them.
- The quality gates or review checkpoints that must run after synthesis.
- References on team topologies, coordination patterns, or example team boards (if available).
Workflow
-
Decide whether parallelism buys time, confidence, or separation of concerns.
- Done when: serial/parallel/worktree-split decision is recorded and communicated to team.
-
Split the work into independent tracks with an owner, expected output, and handoff condition.
- Done when: each track has clear input, output, and ownership + dependencies mapped.
-
Pick a lead agent to maintain the task board, resolve blockers, and synthesize results.
- Done when: lead agent identified and briefed on integration responsibilities.
-
Give each agent a bounded prompt with files, constraints, and stop conditions.
- Done when: each agent has received a scoped brief + stop conditions + file permissions.
-
Run sync points only at dependency boundaries, not continuously.
- Done when: sync schedule defined and agents notified of sync times + escalation paths.
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 · 100 lines · 52 tokens per session scan A 4ea8031dfbf7
orchestrate is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 885 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
ulw-execute
Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.