harness-adapters
Skill2 starsChanged 32 days agoMITView on GitHub
Agent-only reference for firstmate harness operations. Use 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. Contains verified facts for claude, codex, opencode, pi, pi-signed, grok, kimi, cursor, gemini, muse, rovo, omp, agy, and devin.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- kunchenguid/firstmateedited, first seen Oct 8, 2026
- karanmrn/claude-skillstheir own version, first seen Jun 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- kunchenguid/firstmate★ 8.7k90% same
Wrote their own version · 1
- karanmrn/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- afkSkill
- agent-skill-trigger-indexSkill
- ahoySkill
- ask-user-authoritySkill
- away-quiet-supervisionSkill
- bearingsSkill
- bootstrap-diagnosticsSkill
- captain-hold-lifecycleSkill
- control-firstmateSkill
- decision-hold-lifecycleSkill
- diagnostic-reasoningSkill
- firstmate-codexappSkill
- firstmate-coding-guidelinesSkill
- firstmate-orcaSkill
- fmx-respondSkill
- operational-home-layoutSkill
- process-event-sourcesSkill
- project-managementSkill
- quietSkill
- quota-array-dispatchSkill
- scout-completionSkill
- secondmate-provisioningSkill
- session-start-recoverySkill
- ship-landingSkill
- stowSkill
- stuck-crewmate-recoverySkill
- updatefirstmateSkill
- validation-supervisionSkill
- verify-firstmateSkill
- stowSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
When an action spans rows, load the union once rather than every reference.
- Very specific: line 27
Never dispatch a crewmate or secondmate on an unverified adapter.
- Very specific: line 28
If config/crew-harness or config/secondmate-harness names one, tell the captain under ../../../AGENTS.md section 9 that the requested …
- Distinctive: line 29
Do not pause current work for that choice.
- Very specific: line 36
Never type an interrupt key or exit command through fm-send, where routing-marked lifecycle text becomes chat.
- Very specific: line 44
Only FM_PI_HARNESS=pi-signed at the launch boundary together with PI_CODING_AGENT=true selects Pi-signed.
- Distinctive: line 54
Every emitted plan appends the selected or recorded harness reference after the named common references.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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, AGY, and Devin 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 process name omp is its ancestry evidence, as references/harness/omp.md records.
../../../bin/fm-spawn.sh owns worker marker establishment, while the primary launch command in docs/configuration.md owns the signed-primary boundary.
../../../bin/fm-harness.sh crew resolves config/crew-harness, where absent or default means firstmate's own harness.
../../../bin/fm-harness.sh secondmate resolves config/secondmate-harness -> config/crew-harness -> firstmate's own harness.
../../../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"
}
}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

