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.
Borrowing it
Nothing to install: this file belongs to kunchenguid/firstmate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kunchenguid/firstmate/main/.agents/skills/fmx-respond/SKILL.mdgit 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/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/kunchenguid/firstmate/fmx-respond"><img src="https://agentmods.dev/badge/skills/kunchenguid/firstmate/fmx-respond.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 209 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00075 | $0.09373 |
| Opus 5.5 | $0.00030 | $0.03749 |
| Sonnet 5.5 | $0.00015 | $0.01875 |
| Haiku 4.5 | $0.00007 | $0.00937 |
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 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 — 325 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.
- 4d ago Changed · -4 lines · -70 tokens per session 296ffb2b4ae1
- 27d ago Changed · +15 lines 6646f717da76
- 1mo ago Changed · +3 lines 2a0c604a16fb
- 1mo ago Changed 9b174f8dbb49
- 1mo ago Changed 828422b83a9a
- 1mo ago Changed · -1 lines a76a6c747992
- 1mo ago Changed · +28 lines f5bedabe7fb4
- 1mo ago First seen · 284 lines · 145 tokens per session scan A 18fdd2ed62d3
fmx-respond is a skill published in the GitHub repository kunchenguid/firstmate (8,295 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 9,373 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.