Index of every page on this site: llms.txt
All skills
kunchenguid avatar

/harness-adapters

@427056c
by Kun Chenkunchenguid/firstmate9k stars
2,779
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/kunchenguid/firstmate/harness-adapters

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈61 tokens for metadata: the name and description. ≈1.7k when used: this file. ≈41k more on demand in 22 files.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈245 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

harness-adapters

This is the one skill, trigger, and routing owner for harness-specific Firstmate operations. Load this router first, then exactly the common reference and one harness reference selected below. When an action spans rows, load the union once rather than every reference. Files under references/ are resources of this skill, not additional catalogued skills.

Path contract

The skill directory is the directory containing this SKILL.md. Resolve on-demand reference links and relative links to their executable, documentation, or sibling-skill owners against the skill directory, including links named by a nested reference. Operational paths keep the context named by their owner: config/ and active-home settings belong to the active Firstmate home, state/ belongs to that home, and project settings such as .claude/settings.json belong to the target project.

Non-negotiable safety

Never dispatch a crewmate or secondmate on an unverified adapter. If config/crew-harness or config/secondmate-harness names one, tell the captain under ../../../AGENTS.md section 9 that the requested worker runtime is not verified, use firstmate's own verified runtime for current work, and ask only whether to verify the requested runtime for future work. Do not pause current work for that choice.

On unknown, ask the captain instead of guessing. A current captain override beats detection, while a per-task override governs only that dispatch. For recovery and control, use the exact harness= in state/<id>.meta; never infer it from a model or provider.

Deliver lifecycle actions only through ../../../bin/fm-control.sh <task-id> interrupt|exit|relaunch. Never type an interrupt key or exit command through fm-send, where routing-marked lifecycle text becomes chat. Trust handling is complete only when inspection proves the target started processing its instructions; delivery success alone is not proof. Muse, Gemini, Devin, Command Code, Polytoken, Cortex, Kiro, and Hermes are verified only for crewmate and scout work, never a secondmate or primary.

Detection

../../../bin/fm-harness.sh prints firstmate's own harness from verified environment markers and process ancestry, and owns how they combine. A marker names its harness, but a structural ancestor of a different harness outranks it, because a marker is ordinary environment state a child or a multiplexer can retain while ancestry is what proves who owns the process tree. Only FM_PI_HARNESS=pi-signed at the launch boundary together with PI_CODING_AGENT=true selects Pi-signed; shared unmarked launcher ancestry remains Pi. omp publishes no marker of its own; FM_OMP_HARNESS=omp is Firstmate's launch marker and the anchored identity in bin/fm-omp-process-lib.sh (process name omp, or bun running the omp launcher) is its ancestry evidence, as references/harness/omp.md records. ../../../bin/fm-spawn.sh owns worker marker establishment, while the README launch command owns the signed-primary boundary. ../../../bin/fm-harness.sh crew resolves config/crew-harness, where absent or default means firstmate's own harness. docs/configuration.md owns secondmate pin resolution, including per-mate overrides; bin/fm-harness.sh owns the resolver commands. ../../../bin/fm-spawn.sh re-resolves on every spawn, and an explicit per-spawn argument wins for that spawn. A new adapter's verified marker and command name must land in ../../../bin/fm-harness.sh.

Operation-to-reference matrix

Every emitted plan appends the selected or recorded harness reference after the named common references. The harness-adapter-routing-v1 object is the machine-readable and human-visible selection contract: choose the operation, choose the scenario within it, then append the selected harness reference. default is the normal scenario when no narrower scenario applies. Kimi establishes its unsupported primary boundary in its selected harness reference; Muse and Gemini follow Non-negotiable safety above. A new tool remains undispatchable until the verify plan, its harness entry, every named owner, and the live checks land.

{
  "operations": {
    "start": {
      "default": ["references/common/dispatch.md", "references/common/model-and-effort.md"],
      "trust-dialog": ["references/common/control-and-recovery.md"]
    },
    "trust": {"default": ["references/common/control-and-recovery.md"]},
    "skill": {"default": ["references/common/control-and-recovery.md"]},
    "interrupt": {"default": ["references/common/control-and-recovery.md"]},
    "exit": {"default": ["references/common/control-and-recovery.md"]},
    "resume": {"default": ["references/common/control-and-recovery.md"]},
    "recovery": {
      "default": ["references/common/control-and-recovery.md"],
      "replacement-profile": ["references/common/control-and-recovery.md", "references/common/dispatch.md", "references/common/model-and-effort.md"],
      "secondmate": ["references/common/control-and-recovery.md", "references/common/primary-hooks.md"],
      "replacement-secondmate": ["references/common/control-and-recovery.md", "references/common/dispatch.md", "references/common/model-and-effort.md", "references/common/primary-hooks.md"]
    },
    "primary": {"default": ["references/common/primary-hooks.md"]},
    "model-effort": {
      "default": ["references/common/model-and-effort.md"],
      "configured-profile": ["references/common/model-and-effort.md", "references/common/dispatch.md"]
    },
    "verify": {"default": ["references/common/dispatch.md", "references/common/control-and-recovery.md", "references/common/primary-hooks.md", "references/common/model-and-effort.md"]}
  },
  "harnesses": {
    "claude": "references/harness/claude.md",
    "codex": "references/harness/codex.md",
    "opencode": "references/harness/opencode.md",
    "pi": "references/harness/pi.md",
    "pi-signed": "references/harness/pi.md",
    "grok": "references/harness/grok.md",
    "kimi": "references/harness/kimi.md",
    "cursor": "references/harness/cursor.md",
    "gemini": "references/harness/gemini.md",
    "muse": "references/harness/muse.md",
    "rovo": "references/harness/rovo.md",
    "omp": "references/harness/omp.md",
    "agy": "references/harness/agy.md",
    "devin": "references/harness/devin.md",
    "commandcode": "references/harness/commandcode.md",
    "polytoken": "references/harness/polytoken.md",
    "cortex": "references/harness/cortex.md",
    "kiro": "references/harness/kiro.md",
    "hermes": "references/harness/hermes.md"
  }
}

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    This skill is a technical reference for the "firstmate" agent system, providing detailed instructions on how to manage and interact with various AI harnesses (Claude, Codex, OpenCode, Pi, and Grok). It outlines protocols for spawning agents, handling trust dialogs, and verifying new adapters. The analysis found no malicious patterns, prompt injections, or unauthorized data access. It primarily serves to document the technical constraints and expected behaviors of a multi-agent orchestration environment.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 427056c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
user-invocable
false
metadata
{
  "internal": true
}

README badge

README badge for kunchenguid/firstmate/harness-adapters