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 boshu2/agentops --skill orchestrategit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/orchestrate)<a href="https://agentmods.dev/skills/boshu2/agentops/orchestrate"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/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/boshu2/agentops/orchestrate"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/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.00035 | $0.01883 |
| Opus 5.5 | $0.00014 | $0.00753 |
| Sonnet 5.5 | $0.00007 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
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 10d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate
Coordinate caller-authorized work through its existing tracker and runtime. Use the accepted task or conversation; a clear task needs zero mandatory skills. Selecting Orchestrate adds in-session guidance, not an AgentOps scheduler, work index, queue, ownership system, aggregate retry controller or delivery authority. The caller's tracker owns assignments and dependencies; its runtime owns running contexts, bounds and supervision; repository policy owns integration and delivery. Orchestrate decides what each worker does next. Agent Native launches and observes workers; Navigate picks the wave on a bead graph toward frozen acceptance and records verdicts.
Before any dispatch
- Finished is not done. Exit 0, a pushed branch, a closed tracker item or a worker saying "done" makes a candidate. It still owes its checks, integration and, when one is owed, a fresh judgment.
- Drain before starting. While candidates wait on checks, repair, integration or an owed judgment, free capacity goes there first. A free slot alone is not a dispatch reason; start new implementation with what is left.
- Judges did not author. Review or validation of a candidate goes to a context that did not write it.
- Readiness is content. A prerequisite counts only when its bytes are in the intended checkout. A closed item whose change is missing, stale or unavailable there is not ready: hold its dependents, keep its native status, and report the gap.
- Reconcile before resuming. Match tracker assignments against observed runtime state, validators included, before dispatching. Never duplicate an assignment because this conversation lacks it.
Recover the actual work
Read the accepted outcome, examples and scope from their current owner. Recover settled caller choices and rationale, completed history, consequential open questions and the next investigation from the existing native handoff. Do not repeat settled interviews or require the full transcript. Missing or contradictory pointers require source investigation, not a guessed decision.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · +15 lines · +2 tokens per session 2bebe3319ff9
- 12d ago Changed · +25 lines 78bf792f672e
- 20d ago Changed · -17 lines 11e24b19cf7d
- 21d ago Changed · +2 lines eb861d1705a1
- 23d ago First seen · 145 lines · 33 tokens per session scan A 2e3bc6e69a40
orchestrate is a skill published in the GitHub repository boshu2/agentops (448 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,883 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-09-23.
Other skills, from other repositories
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
git-history-analysis
Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.
atomic-issues-prs
Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.
graph-backbone
Use when defining, revising, or gate-replanning the project structural backbone in project-root graph.yaml; produces a validated approved revision preserving immutable topology and additive metadata. Not for remote, credential, publish, deploy, or irreversible changes.