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 andsnw/orca --skill orca-lineargit clone --depth 1 https://github.com/andsnw/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/andsnw/orca/orca-linear)<a href="https://agentmods.dev/skills/andsnw/orca/orca-linear"><img src="https://agentmods.dev/badge/skills/andsnw/orca/orca-linear/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/andsnw/orca/orca-linear"><img src="https://agentmods.dev/badge/skills/andsnw/orca/orca-linear.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.00070 | $0.00489 |
| Opus 5.5 | $0.00028 | $0.00196 |
| Sonnet 5.5 | $0.00014 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
orca-linear 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 1mo 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.
This is a copy
100% identical to orca-linear — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Orca Linear
This discovery stub loads the version-matched guide from the Orca executable used for this session.
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 orca-linear
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.
- 1mo ago Changed · +2 lines 8da23ef96470
- 1mo ago Changed · -35 lines · -75 tokens per session 85ee0d4d3cfa
- 1mo ago First seen · 79 lines · 145 tokens per session scan A 39241e0aa292
orca-linear is a skill published in the GitHub repository andsnw/orca (0 stars, last pushed 25d ago), licensed MIT. It adds 70 tokens to every session and 489 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to orca-linear, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…