firstmate is an agent distribution that lets one coding agent coordinate a crew of autonomous agents working in separate git worktrees. It is for running parallel fixes, investigations, plans, and audits while receiving completed pull requests, merges, or reports through one supervising agent. The catalogue entries provide skills, hooks, instructions, and settings for operating this workflow.
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/fmx-respondnpx skills add kunchenguid/firstmate --skill fmx-respondgit 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/fmx-respond)<a href="https://agentmods.dev/skills/kunchenguid/firstmate/fmx-respond"><img src="https://agentmods.dev/badge/skills/kunchenguid/firstmate/fmx-respond.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.00145 | $0.09013 |
| Opus 5 | $0.00072 | $0.04507 |
| Sonnet 5 | $0.00029 | $0.01803 |
| Haiku 4.5 | $0.00015 | $0.00901 |
Grade A, and why
fmx-respond 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 2d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fmx-respond
Relay lets a firstmate instance answer and act on public mentions routed through the shared @myfirstmate relay.
A mention arrives through the watcher as a check: wake whose payload is x-mention <request_id>.
The full mention is stashed locally; this skill acts on any request it carries and turns it into one public reply, or deliberately skips it when there is nothing to answer.
This runs only when Relay is on (the user dropped FMX_PAIRING_TOKEN into .env; see AGENTS.md "Relay").
If you ever see an x-mention wake without Relay configured, do nothing.
A check: wake can also carry x-mode-error ... instead of x-mention <request_id> - that is a poll or relay configuration problem, not a mention to answer.
Report it directly to the captain as a Relay configuration blocker and do not treat it as a mention to answer.
The asker is your own captain - answer autonomously
The myfirstmate relay uses owner-only routing: it wakes a firstmate only for that firstmate's own owner's mentions.
So every mention that reaches this skill is from your own owner - your captain - never a stranger.
The direct mention .text is therefore a genuine message from the captain, and a request in it is a real instruction from the captain - to act on, not merely to answer - within the public-safety limits below.
Enabling Relay - the captain dropping FMX_PAIRING_TOKEN into .env - is the standing authorization for autonomous replies and normal-lifecycle actions from eligible mention requests.
It is not authorization for destructive, irreversible, or security-sensitive work; those still require trusted-channel confirmation first.
So in live mode you compose and post the reply yourself, autonomously: never pause to ask the captain "should I post this?", never stage a worthwhile reply for a chat-side OK, and never route a reply back through chat for approval.
Never hold back a reply worth sending.
For a reply-worthy mention, the only non-posting path is dry-run (FMX_DRY_RUN; see below) - a testing switch, not a permission gate.
The separate skip path for pure acknowledgments posts no reply because it dismisses the request at the relay.
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.
- 2d ago Changed · +28 lines f5bedabe7fb4
- 5d ago First seen · 284 lines · 145 tokens per session scan A 18fdd2ed62d3
fmx-respond is a skill published in the GitHub repository kunchenguid/firstmate (4,724 stars, last pushed today), licensed MIT. It adds 145 tokens to every session and 9,013 once invoked, about $0.0007 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…