firstmate: Skill for Claude Code

.agents/skills/agent-skill-trigger-index/SKILL.md

agent-skill-trigger-index is a skill for Claude Code from kunchenguid/firstmate. It costs 20 tokens per session (1,124 once invoked), scanned A, original, MIT.

An index of the conditions that cause internal agent skills to load. It maps startup diagnostics, bug reports, user decisions, worker recovery, and other events to the relevant procedure.

In plain words
What is it for?
Use it when auditing or maintaining the complete trigger list for agent-only skills.
Why use it?
It helps the agent load the right internal guidance at the right time instead of missing a required procedure or loading one unnecessarily.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is kunchenguid/firstmate's own configuration. It tells Claude Code how to work on firstmate itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything firstmate configures →

About the project

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.

kunchenguid/firstmate · 8,295 stars · on GitHub

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/kunchenguid/firstmate/main/.agents/skills/agent-skill-trigger-index/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kunchenguid/firstmate

Made for: Claude Code.

Wrote 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.

agentmods badge for agent-skill-trigger-index

README.md
[![agentmods](https://agentmods.dev/badge/skills/kunchenguid/firstmate/agent-skill-trigger-index/github.svg)](https://agentmods.dev/skills/kunchenguid/firstmate/agent-skill-trigger-index)
Your own site
<a href="https://agentmods.dev/skills/kunchenguid/firstmate/agent-skill-trigger-index"><img src="https://agentmods.dev/badge/skills/kunchenguid/firstmate/agent-skill-trigger-index/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.

agentmods 80×15 button for agent-skill-trigger-index

Your own site · 80×15
<a href="https://agentmods.dev/skills/kunchenguid/firstmate/agent-skill-trigger-index"><img src="https://agentmods.dev/badge/skills/kunchenguid/firstmate/agent-skill-trigger-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,124 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.01124
Opus 5.5 $0.00008 $0.00450
Sonnet 5.5 $0.00004 $0.00225
Haiku 4.5 $0.00002 $0.00112

Measured 2d ago against content hash 40151c28964c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-skill-trigger-index 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.

.agents/skills/agent-skill-trigger-index/SKILL.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent-only reference skills

These skills are not captain-invocable; load them only at their precise triggers.

  • operational-home-layout - load when locating, interpreting, or changing Firstmate home, config, data, state, project, or generated runtime paths.
  • session-start-recovery - load when the session-start digest reports unfinished checks, actionable diagnostics, recovery inputs, or output requiring interpretation.
  • bootstrap-diagnostics - load whenever the session-start digest's bootstrap or network-checks section prints an actionable diagnostic line (MISSING:, MISSING_MANUAL:, OUTDATED:, PRESENTATION_UNAVAILABLE:, BACKEND_INVALID:, NEEDS_GH_AUTH, TANGLE:, STARTUP_MEMORY_BUDGET:, CREW_DISPATCH: invalid, FLEET_SYNC:, NETWORK_CHECKS:, HOME_SUMMARY:, BACKLOG_RECONCILE:, SECONDMATE_SYNC:, SECONDMATE_LIVENESS:, SECONDMATE_HANDOFF:, NUDGE_SECONDMATES:, or FMX:), or when BOOTSTRAP_INFO: says an interrupted backlog cleanup may have left an endpoint or local copy; silence and other BOOTSTRAP_INFO: facts need no load.
  • diagnostic-reasoning - load before scoping a reported bug and before acting on a diagnostic report.
  • ask-user-authority - load before deciding any ask-user finding.
  • validation-supervision - load when a ship starts or already has an active no-mistakes validation run, including a mid-run requirement change or finding, and before deciding or answering any ask-user finding.
  • ship-landing - load when a ship reports a PR or ready branch, when deciding or monitoring landing, and before task cleanup.
  • scout-completion - load when a scout reports completion, presents a visual artifact for iteration, or is being considered for promotion to implementation.
  • quota-array-dispatch - load before choosing among a matched crew-dispatch profile array from current quota-axi default TOON.
  • harness-adapters - load before spawning or recovering a crewmate or secondmate, handling a trust dialog, sending a harness-specific skill invocation, interrupting or exiting an agent, resuming an exited agent, or verifying a new harness adapter.
  • firstmate-orca - load before switching to Orca, spawning or supervising Orca-backed work, smoke-testing Orca backend behavior, debugging Orca task state, or reconciling Orca-backed task metadata.
  • project-management - load before adding, creating, removing, or initializing a project. Cloning or registering a project is add intake and uses the same trigger.
  • stuck-crewmate-recovery - load when the session-start digest reports an ordinary direct report's endpoint dead or its metadata has no window, after a stale wake, looping pane, repeated confusion, an answered-by-brief question, an unresponsive crewmate, or a failed steer, and whenever a live worker reports its no-mistakes pipeline dead, unreachable, or timed out.
  • secondmate-provisioning - load before creating, seeding, validating, launching, handing backlog to, recovering, pushing inherited local material into, or retiring a secondmate home, and before editing data/secondmates.md.
  • captain-hold-lifecycle - load before treating an investigation or visual review as complete, before ending a visual review that exposed a captain decision, when recording or routing the captain's answer, and on any RECORD DIVERGENCE line from the wake drain.
  • away-quiet-supervision - load whenever /afk or /quiet is invoked, an away or quiet record exists, or a marked away-supervisor message arrives.
  • process-event-sources - load before arming a long-polling source, before registering a deterministic condition->action watch (do X as soon as Y is true), on any procevent <adapter> <source-id> <sequence> check wake, and on any process-event source stranded or process-event source failed to start check wake. Never run a registered source's blocking command yourself in a conversational turn.
  • fmx-respond - load on an x-mention <request_id> check: wake to handle the mention, on an x-mode-error ... check: wake to report the Relay configuration blocker, on a public-followup ... check: wake or a startup-surfaced public commitment, and on any milestone or terminal wake for a Relay-linked task before posting its completion follow-up; relevant only when Relay is on.
  • firstmate-codexapp - load before coordinating a visible Codex Desktop thread, evaluating a Codex App backend request, or reconciling Codex Desktop host-tool smoke evidence for Firstmate work.
  • firstmate-coding-guidelines - load before changing firstmate's shared, tracked material, as defined by section 1's list, whether editing directly or briefing a crewmate for a firstmate-repo task.

Read the full file on GitHub · 35 lines

Changes

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.

  1. 2d ago Changed 40151c28964c
  2. 17d ago Changed · +6 lines 781128f425f8
  3. 27d ago First seen · 29 lines · 20 tokens per session scan A b5dda7f71a36

Subscribe to this mod's changes

agent-skill-trigger-index is a skill published in the GitHub repository kunchenguid/firstmate (8,295 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,124 once invoked, about $0.0001 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-09-28.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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.

microsoft/vscode · 53 tokens