Borrowing it
Nothing to install: this file belongs to Traves-Theberge/Orchestra. 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/Traves-Theberge/Orchestra/main/.codex/skills/maestro-github/SKILL.mdgit clone --depth 1 https://github.com/Traves-Theberge/OrchestraWrote 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/traves-theberge/orchestra/maestro-github)<a href="https://agentmods.dev/skills/traves-theberge/orchestra/maestro-github"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/maestro-github/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/traves-theberge/orchestra/maestro-github"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/maestro-github.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.00031 | $0.00546 |
| Opus 5.5 | $0.00012 | $0.00218 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
maestro-github 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 19d 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.
What it actually says
GitHub for Maestro
Read maestro-integrations for the shared journey and orchestra-cli for executable task controls. Resolve exact owner/repo from registered project metadata or a verified Git remote; Maestro's control directory is not a repository. Match PR base repository to that identity before linking it to a task.
When gh is available, reuse its existing signed-in account. Verify an authenticated repository read before claiming access. Use explicit scope from the control directory:
gh repo view OWNER/REPO --json nameWithOwner,url,viewerPermission
gh issue list --repo OWNER/REPO --json number,url,title,assignees,state
gh pr list --repo OWNER/REPO --json number,url,title,state,headRefName,baseRefName
gh pr view NUMBER --repo OWNER/REPO --json number,url,state,headRefOid,headRefName,baseRefName,reviewDecision,statusCheckRollup
These commands read GitHub; they do not attach a PR to an Orchestra task. Preserve the task's persisted pr_url, and verify the remote PR repository/head/status separately. An empty open-PR list does not prove no historical PR is linked. Inspect explicit linked PRs even when closed or merged.
For issue-backed tasks, select an actual GitHub issue source connection; local SQLite tasks remain local even when their project has a GitHub remote. Use advertised source-scoped create/assign controls and receipts. GitHub issue numbers collide between repositories; a GitHub assignee is a login, while an Orchestra worker/harness is a separate identity. Do not infer execution from assignment or treat GitHub open/closed as the complete Kanban lifecycle.
GitHub's add-assignee endpoint is additive and may silently ignore users without permission. When the shared adapter supports assignment, confirm the requested login in the returned issue and preserve concurrent assignees; do not claim atomic remote compare-and-set. A timed-out external mutation remains uncertain and must not be replayed with a new UUID.
For authorized repository/PR actions, inspect installed CLI help and use the user's requested scope. Do not change credentials or permissions to resolve an error. UI review discussions, checks, and the reviewed head are distinct evidence; report any missing observation.
Primary API reference: GitHub issue assignees. Native GitHub CLI access does not prove that another harness or the backend tracker uses the same credential.
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.
- 19d ago First seen · 28 lines · 31 tokens per session scan A 7ea6c4dabb5a
maestro-github is a skill published in the GitHub repository Traves-Theberge/Orchestra (26 stars, last pushed 10d ago), licensed Apache-2.0. It adds 31 tokens to every session and 546 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-10-06.
Other skills, from other repositories
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
start-task
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.