Orca is an application for running and coordinating multiple coding agents, giving each agent an isolated Git worktree while tracking their work in one place. Developers use it to run agents such as Codex, ClaudeCode, OpenCode, or Pi in parallel across desktop, mobile, local terminals, or remote servers.
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 stablyai/orca --skill linear-ticketsgit clone --depth 1 https://github.com/stablyai/orcaWrote 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/stablyai/orca/linear-tickets)<a href="https://agentmods.dev/skills/stablyai/orca/linear-tickets"><img src="https://agentmods.dev/badge/skills/stablyai/orca/linear-tickets/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/stablyai/orca/linear-tickets"><img src="https://agentmods.dev/badge/skills/stablyai/orca/linear-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00085 | $0.00522 |
| Opus 5.5 | $0.00034 | $0.00209 |
| Sonnet 5.5 | $0.00017 | $0.00104 |
| Haiku 4.5 | $0.00009 | $0.00052 |
Grade A, and why
linear-tickets 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 27d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- linear-tickets — 100% identical, 0 lines differ
- linear-tickets — 100% identical, 0 lines differ
What it actually says
Linear Tickets (Legacy Name)
This discovery stub uses the legacy name linear-tickets for orca-linear; both use
ORCA linear .... Load the version-matched guide below.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
ORCA_CLI_COMMANDenvironment variable is set, use its value. Orca exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT, useorca-dev. - Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide. Never run bareorcathere — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine. - Otherwise, use
orca.
Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run ORCA literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.
Load the version-matched guide before running Orca commands
ORCA skills get linear-tickets
Prefer --json. Use the selected executable's --help for commands or flags the guide does
not cover. If a command reports that Orca is not running, start it with ORCA open --json
and retry. If it fails with runtime_access_denied, your sandbox blocked the connection:
re-run it with escalated permissions, and do not run ORCA open or restart Orca. If
skills get is unknown, explain that updating Orca restores the guide; use --help for
read-only discovery and do not guess unsupported commands.
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.
- 27d ago Changed · +2 lines e181f86073da
- 1mo ago Changed · -35 lines · -75 tokens per session af2d33d98c21
- 1mo ago First seen · 81 lines · 160 tokens per session scan A d2dec89eca8c
linear-tickets is a skill published in the GitHub repository stablyai/orca (99,715 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 522 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
feedback
Collect and submit feedback about Superset (bug reports, feature requests, or general feedback) privately to the Superset team or as a public GitHub issue. Use when the user wants to report a Superset bug, request a feature, or send feedback about Superset.
issue-triage
Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels, milestone, and assignee. Use when the user asks to triage an issue, sort the backlog, deal with new issues, check whether a bug is already reported, or says "what should we do with this issue".
duplicate-sweep
Find and merge duplicate Linear issues — group reports of the same underlying bug, pick the survivor, and move the evidence across. Use when the backlog has grown noisy, someone asks whether an issue is already reported, or you are cleaning up before planning.
file-issue
Turn a rough report into a Linear issue someone can pick up — reproduce the claim, check for duplicates, and fill in team, priority, and labels. Use when the user says to file, open, or create an issue, hands over a bug report or error, or asks to get something into Linear.
project-status
Draft a Linear project status update from what actually moved — progress, risks, and the one decision that needs making. Use when someone asks for a project update, a status post, where a project stands, whether it will land on time, or what to tell stakeholders.
find-in-circleback
Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword, read the notes before the transcript, and cite the meeting behind every claim. Use when the user asks what happened on a call, what a customer or teammate said, what was agreed, or refers…