Compozy is a system for coordinating AI coding agents, allowing command-line agents to divide work, exchange tasks, run scheduled or repeated jobs, and share project memory under browser supervision. Developers and technical operators use it to create, automate, and monitor ongoing agent work. The catalogue entries provide skills and other add-ons for its agent workflows.
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 compozy/compozy --skill cy-orquestrate-issuegit clone --depth 1 https://github.com/compozy/compozyWrote 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/compozy/compozy/cy-orquestrate-issue)<a href="https://agentmods.dev/skills/compozy/compozy/cy-orquestrate-issue"><img src="https://agentmods.dev/badge/skills/compozy/compozy/cy-orquestrate-issue/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/compozy/compozy/cy-orquestrate-issue"><img src="https://agentmods.dev/badge/skills/compozy/compozy/cy-orquestrate-issue.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.00094 | $0.01743 |
| Opus 5.5 | $0.00038 | $0.00697 |
| Sonnet 5.5 | $0.00019 | $0.00349 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
cy-orquestrate-issue 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Issue Resolution
The orchestrator investigates and dispatches; a dedicated CompozyOS session implements each issue through PR delivery.
Contract and inputs
- Accept issue numbers/URLs or a bug report with screenshots, logs, or reproduction steps. Resolve the repository from the workspace remote; ask only if the target remains ambiguous.
- Default executor: agent
general, providerclaude, modelclaude-opus-5-5, reasoning effortmedium. Explicit user overrides win. Verify the effective runtime; never silently substitute a model. - Create one new managed worktree and new logical session per issue. Follow-ups for that issue go to its recorded session. Never repurpose an unrelated active session.
- An invocation to resolve issues authorizes the scoped issue, branch, push, PR, review replies, and review-remediation work. It does not authorize merge, destructive Git, deleting worktrees, installing reviewers, or changing the user's host runtime. Existing session authorization wins.
- Default orchestration ends after verified dispatch, with the executor responsible for the full delivery contract. If asked to accompany delivery, supervise until that contract is satisfied. A launch report must say in progress, never that the issue is resolved.
1. Load the runtime contract
Use the active harness to resolve compozy__skill_view. Load the Compozy skill and the full
references selected by its router for tools, worktrees, sessions, and orchestration:
references/tools-and-skills.md, references/native-tools.md, references/worktrees.md,
references/runtime-operations.md, and references/tasks-and-orchestration.md. Reuse complete
current reads from this session. Follow source-qualified command_id and retained-result
continuation instructions when supplied.
Discover capabilities with compozy__tool_search and inspect live descriptors with
compozy__tool_info. The canonical IDs below are discovery keys, not harness invocation names.
Use the returned references and current schemas. A denied tool/skill read is not permission to
bypass policy through CLI or filesystem access.
What ships with it
1 file 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.
- 5d ago Changed · +2 lines · +2 tokens per session 003320672373
- 9d ago Changed · +8 lines 8d7d5c3f424a
- 1mo ago First seen · 108 lines · 92 tokens per session scan A 0ffe7386af61
cy-orquestrate-issue is a skill published in the GitHub repository compozy/compozy (2,817 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 1,743 once invoked, about $0.0004 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-12.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.