Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. 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/usk6666/yorishiro-proxy/main/.claude/skills/orchestrate/SKILL.mdgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote 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/usk6666/yorishiro-proxy/orchestrate)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/orchestrate"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/orchestrate.svg" alt="Measured on agentmods" 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.00026 | $0.06502 |
| Opus 5 | $0.00013 | $0.03251 |
| Sonnet 5 | $0.00005 | $0.01300 |
| Haiku 4.5 | $0.00003 | $0.00650 |
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 8d 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 — 616 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orchestrate
An orchestration skill that understands milestones, analyzes dependencies, and delegates implementation of multiple Linear Issues to sub-agents.
Arguments
/orchestrate— Analyze active milestones and suggest the next Issues to implement/orchestrate <Issue ID> [Issue ID...]— Implement specified Issues considering dependencies/orchestrate milestone <name>— Implement Issues in the specified milestone in dependency order/orchestrate status— Show all milestone progress + running sub-agent status
Steps
Phase 0: Product Understanding — Milestone and Current State Overview
Do this first on every run. The orchestrator first adopts the product owner's perspective.
0-1. Fetch All External Context (Parallel)
Launch all of the following in a single parallel batch (5 calls total):
mcp__linear-server__list_milestones(project=yorishiro-proxy)mcp__linear-server__get_document(id=d413edd7-d296-433a-ab94-11d4dd57d883)(roadmap)mcp__linear-server__list_issues(team=Usk6666, project=yorishiro-proxy, state=started)mcp__linear-server__list_issues(team=Usk6666, project=yorishiro-proxy, state=backlog)mcp__linear-server__list_issues(team=Usk6666, project=yorishiro-proxy, state=unstarted)
0-2. Process Fetched Data
From the milestone list, classify progress:
progress == 100→ Complete0 < progress < 100→ Active (in progress)progress == 0→ Not started
From the roadmap document, extract:
- Product goal: What is being built and for whom
- Milestone structure: The goal and delivered value of each milestone
- Inter-milestone dependencies: Which milestone depends on which
- Issue ordering within milestones: Natural implementation order of Issues within each milestone
- Technical decisions: Design decisions already made (storage choice, protocol strategy, etc.)
Group fetched Issues by projectMilestone field.
Do not fetch completed Issues. Use milestone progress + roadmap Issue table to track completion status.
Only fetch specific completed Issues individually with get_issue(id) when needed for building dependency context.
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.
- 8d ago First seen · 616 lines · 26 tokens per session scan A b2915f7103d6
orchestrate is a skill published in the GitHub repository usk6666/yorishiro-proxy (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 6,502 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
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
pipefy-members-email-webhooks
Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks. Covers 12 MCP tools.
pipefy-relations
Use this skill when the user wants to link pipes, tables, or cards across workflows — creating or managing pipe relations, table relations, or card relations. Covers 8 MCP tools.
servicenow-change-management
ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use…