Read Session
asgeirtj/system_prompts_leaks
Locate and read Muse Code's OWN session logs — the current session or a prior one.
Inspect Harness sessions, explain activity and resource readings, preview cleanup, and stop or open explicitly selected sessions through their owning daemons.
MITAuto-check passed
Install Fleet Operations
$ npx skills add autonomous-ai/openharness --skill fleet-operations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install autonomous-ai/openharness fleet-operations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/store/agents/harness-monitor/skills/fleet-operations .claude/skills/fleet-operations && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fleet-operations" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operations into .claude/skills/fleet-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fleet-operations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add autonomous-ai/openharness --skill fleet-operations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install autonomous-ai/openharness fleet-operations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/store/agents/harness-monitor/skills/fleet-operations .agents/skills/fleet-operations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fleet-operations" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operations into .agents/skills/fleet-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fleet-operations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add autonomous-ai/openharness --skill fleet-operations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install autonomous-ai/openharness fleet-operations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/store/agents/harness-monitor/skills/fleet-operations .cursor/skills/fleet-operations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fleet-operations" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operations into .cursor/skills/fleet-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fleet-operations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/autonomous-ai/openharness.git --path store/agents/harness-monitor/skills/fleet-operations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add autonomous-ai/openharness --skill fleet-operations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install autonomous-ai/openharness fleet-operations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/store/agents/harness-monitor/skills/fleet-operations .gemini/skills/fleet-operations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fleet-operations" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operations into .gemini/skills/fleet-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fleet-operations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install autonomous-ai/openharness fleet-operationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add autonomous-ai/openharness --skill fleet-operations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .github/skills && cp -r skills-src/store/agents/harness-monitor/skills/fleet-operations .github/skills/fleet-operations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fleet-operations" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operations into .github/skills/fleet-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fleet-operations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add autonomous-ai/openharness --skill fleet-operations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install autonomous-ai/openharness fleet-operations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/store/agents/harness-monitor/skills/fleet-operations .opencode/skills/fleet-operations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fleet-operations" agent skill from https://github.com/autonomous-ai/openharness/tree/main/store/agents/harness-monitor/skills/fleet-operations into .opencode/skills/fleet-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fleet-operations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fleet-operations- GitHub stars
- 1.1k
- Token cost
- ~840 tokens
- SKILL.md length
- 443 words
- Files
- 3 (incl. references)
- Skills in repo
- 100
- Repo updated
- First seen
- Licence
- MIT
At a glance
Inspect Harness sessions, explain activity and resource readings, preview cleanup, and stop or open explicitly selected sessions through their owning daemons.
- SKILL.md covers Actions, Close harnesses outside tabs and Cleanup rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Fleet Operations is an agent skill from autonomous-ai/openharness. Inspect Harness sessions, explain activity and resource readings, preview cleanup, and stop or open explicitly selected sessions through their owning daemons.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/policy.md` and `references/signals.md`).
The repository describes itself as: The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across… The licence is MIT.
Example prompts
- “/fleet-operations”
What it can do on your machine
Read from SKILL.md and the folder at commit 50da5db. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fleet Operations loads about 840 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 443 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from autonomous-ai/openharness at commit 50da5db, republished under its MIT licence (© autonomous-ai). 443 words, ~840 tokens.
Download SKILL.mdSave it as
.claude/skills/fleet-operations/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- fleet-operations
- description
- Inspect Harness sessions, explain activity and resource readings, preview cleanup, and stop or open explicitly selected sessions through their owning daemons.
Fleet operations
The table is the primary interface. Use this skill when the person asks the assistant to investigate sessions or review cleanup. Do not start work simply because the monitor opened.
Start with "$HPS_CLI" ls --json --all --machines. Read references/signals.md
before explaining activity or resource readings. Use composite machine/agent IDs when names or IDs
are ambiguous. Missing measurements are unknown; an offline machine is not a stopped session.
Actions
hps show <ref> --machines --jsonreads one session.hps stop <ref> --machines --jsonasks its owning daemon to stop the process and retain history.hps open <ref> --machines --jsonrestores saved launch settings. CheckresumeMode: conversation, fresh conversation, or shell. Do not promise every engine resumes the same conversation.hps stop --policy --machines --jsonpreviews cleanup;--applyapplies the current plan.hps cleanup --machines --jsonpreviews harnesses outside all open tabs;--applycloses them. Background tabs and local utility tabs such as Companions stay open.hps open --stopped --machines --jsonpreviews reopening stopped sessions;--applyexecutes it.
For more than two sessions, show the dry run with reasons and obtain approval before applying it, unless those targets are already authorized.
Recheck the plan after approval; if the targets changed, present the new targets. Named actions must
still correspond to the person's request. Never use --force unless explicitly requested for those
sessions. The row's × button is an explicit single-session stop and may interrupt work in progress.
The daemon owns process identity, stopping and open configuration on local and linked machines.
Do not signal PIDs, reconstruct engine flags, respawn a tmux pane, or edit the registry. After a timeout,
read the original open receipt; do not invent a new operation to compensate. Explain refusals and
uncertain outcomes. Receipts are recorded in ~/.harness/monitor/log.jsonl.
Show full SKILL.md (153 more words)Show less
Close harnesses outside tabs
Use hps cleanup only when the person asks to close harnesses outside their tabs. Review the names
and activity first: it includes working and unknown activity and can end unfinished work. The owning
daemon rechecks open tabs and session identity and saves history before closing. Never bypass those
guards. Report offline machines, unsupported versions, save failures and unconfirmed closes.
Cleanup rules
references/policy.md explains the proposal rules. They never run automatically.
Working sessions, questions, pins, unavailable controls and unknown activity are protected by default.
These policy rules do not use the open-tab guard of the separate hps cleanup command.
Rules and pins live in ~/.config/harness/policy.jsonc. Preserve comments and simulate a proposed
change before applying it. Do not change thresholds to make a refused cleanup succeed.
Never delete transcripts or project folders. Stopping a process can interrupt unfinished work, even though its history is retained. Report what the tools actually confirmed.
© autonomous-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in store/agents/harness-monitor/skills/fleet-operations of autonomous-ai/openharness.
- SKILL.md
- references/policy.md
- references/signals.md
Open the folder on GitHubat commit 50da5db
Compare with similar skills
Fleet Operations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fleet Operations this skillautonomous-ai/openharness | 1.1k | — | ~840 | Automated safety check: Pass | MIT | |
| Read Sessionasgeirtj/system_prompts_leaks | 69k | — | ~2.4k | Automated safety check: Pass | CC0-1.0 | |
| Fleet Manager for Agent Sessionsasgeirtj/system_prompts_leaks | 69k | — | ~2.5k | Automated safety check: Pass | CC0-1.0 | |
| Session History Searchslopus/happy | 24k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Session Handoffsickn33/agentic-awesome-skills | 47k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Coding Agent Session Findercode-yeongyu/oh-my-openagent | 70k | 1 repos | ~2.8k | Automated safety check: Pass | Custom licence |
Similar skills
Fleet Manager for Agent Sessions
asgeirtj/system_prompts_leaks
Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
Session Handoff
sickn33/agentic-awesome-skills
A skill your agent uses when context approaches capacity, before /clear or /compact, when switching tasks, or when ending a coding session: produces a structured handoff artifact for the next session.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
- Official
Session
anthropics/claude-for-legal
Run a focused N-question study session on a subject — MBE, essay, or flashcards.
More from autonomous-ai/openharness
All 100 skills in this repoG-code Slicer Tool
autonomous-ai/openharness
Slices 3D mesh files into printer-profiled plain G-code through real slicer CLIs, with backend discovery, input inspection, dry runs and static validation.
Home Assistant Automation Builder
autonomous-ai/openharness
Turns a home-automation request into standard, testable automations.yaml, run against Home Assistant Core's real triggers and verified with its own trace tool.
Score Music Composer
autonomous-ai/openharness
Turns a musical brief into LilyPond concert-pitch music, checked parts for each instrument and a playable practice pack.
OrcaSlicer 3MF and G-code Workflow
autonomous-ai/openharness
Turns an STL and explicit printer and material requirements into compared OrcaSlicer plans, an editable 3MF project, checked G-code and a portable handoff.
Sheets and Docs Report Builder
autonomous-ai/openharness
Builds an editable DOCX report, a formula-driven XLSX workbook and a fresh LibreOffice PDF preview from one structured source file, then checks them together.
Bambu Labs
autonomous-ai/openharness
Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain .gcode, using Bambu LAN FTPS/MQTT handoffs.
Questions about Fleet Operations
What does Fleet Operations do?
Inspect Harness sessions, explain activity and resource readings, preview cleanup, and stop or open explicitly selected sessions through their owning daemons. Fleet Operations is an agent skill from autonomous-ai/openharness. Inspect Harness sessions, explain activity and resource readings, preview cleanup, and stop or open explicitly selected sessions through their owning daemons.
How do I install Fleet Operations in Claude Code?
Run `npx skills add autonomous-ai/openharness --skill fleet-operations -a claude-code`. Or copy the skill folder (store/agents/harness-monitor/skills/fleet-operations in autonomous-ai/openharness) into .claude/skills/fleet-operations in your project. Claude Code loads it when a task matches its description.
How do I install Fleet Operations in Codex?
Run `npx skills add autonomous-ai/openharness --skill fleet-operations -a codex`. Or copy the skill folder (store/agents/harness-monitor/skills/fleet-operations in autonomous-ai/openharness) into .agents/skills/fleet-operations in your project. Codex loads it when a task matches its description.
Can I use Fleet Operations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add autonomous-ai/openharness --skill fleet-operations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fleet-operations, .gemini/skills/fleet-operations, .github/skills/fleet-operations and .opencode/skills/fleet-operations in your project.
What does Fleet Operations need to run?
SKILL.md names no scripts, command-line tools or credentials: Fleet Operations is instructions for the agent only.
Does Fleet Operations access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Fleet Operations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fleet Operations use?
Fleet Operations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fleet Operations use?
About 840 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 861 tokens, read only when the agent opens those files.
What are the alternatives to Fleet Operations?
Skills that share tags, products or a category with Fleet Operations: Read Session (asgeirtj/system_prompts_leaks, 69k stars), Fleet Manager for Agent Sessions (asgeirtj/system_prompts_leaks, 69k stars), Session History Search (slopus/happy, 24k stars) and Session Handoff (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fleet Operations?
autonomous-ai (a GitHub organization) maintains it in autonomous-ai/openharness, which has 1,149 GitHub stars. The repository holds 100 skills in this directory. The repository was last updated on October 8, 2026.
Source: autonomous-ai/openharness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.