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 agentmods add skills/kunchenguid/firstmate/firstmate-orcanpx skills add kunchenguid/firstmate --skill firstmate-orcagit clone --depth 1 https://github.com/kunchenguid/firstmateWrote 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/kunchenguid/firstmate/firstmate-orca)<a href="https://agentmods.dev/skills/kunchenguid/firstmate/firstmate-orca"><img src="https://agentmods.dev/badge/skills/kunchenguid/firstmate/firstmate-orca.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 | $0.00056 | $0.01245 |
| Opus 5 | $0.00028 | $0.00622 |
| Sonnet 5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
firstmate-orca 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
firstmate-orca
Use this as the operator checklist for Firstmate's experimental Orca runtime backend.
It does not replace AGENTS.md, docs/orca-backend.md, or harness-adapters.
Orca is a runtime backend, not an agent harness.
The runtime backend owns the task endpoint and, for Orca, the task worktree.
The harness is the agent process launched inside that endpoint, such as claude, codex, opencode, pi, pi-signed, grok, or kimi.
Load harness-adapters for harness-specific launch, interrupt, resume, trust-dialog, and skill-invocation facts.
Implementation details, metadata fields, teardown guarantees, and limitations live in docs/orca-backend.md.
docs/verification/runtime-backends.md "Orca" owns active smoke evidence.
Prefer the bin/fm-* helpers over raw orca commands.
Use raw orca only when the helper surface cannot answer the inspection question, and keep the recorded firstmate metadata as the task identity.
Preflight
Work from the current firstmate home or repo root.
If FM_HOME is set, remember that operational state lives under $FM_HOME while the helper scripts still run from this repo's bin/.
Before switching or spawning against Orca:
- Confirm Orca is intentionally selected through
--backend orca,FM_BACKEND=orca, or localconfig/backend. - Confirm the Orca app is running and the backend readiness checks pass before expecting spawn to work.
- Inspect active
state/*.metarecords before changing backend selection. - Treat a backend switch as affecting future spawns only; existing tasks keep their recorded backend.
- Reconcile watcher wakes before unrelated work, especially if Orca tasks are already in flight.
Spawn
Use bin/fm-spawn.sh so firstmate creates the brief, worktree, terminal, metadata, status file, and watcher surface together.
Pass --backend orca for a one-off Orca task, or rely on the already-selected Orca backend when that selection is intentional.
After spawn, check the task with firstmate helpers:
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.
- 4d ago First seen · 93 lines · 56 tokens per session scan A 7755df04d88c
firstmate-orca is a skill published in the GitHub repository kunchenguid/firstmate (4,724 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,245 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…