agentleFS
fmindfmind/dot/skills/agent-harnesses/SKILL.md

agent-harnesses

Skill13 starsChanged 3 days agoMITView on GitHub

Operate and configure Claude Code, Copilot, and OpenCode.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Agent Harnesses

Operate the selected coding-agent host without conflating its configuration, permissions, or lifecycle with another host. Antigravity has its own agy owner. Claude Code has no guide here: use its built-in help and the docs index.

Workflow

  1. Check the version-specific reference before declaring a feature unavailable: installed help can omit supported flags.
  2. Resolve precedence and permission scope before changing execution behavior: hooks and extensions execute code.
  3. Verify the result and the host's own instruction or skill discovery. Use agent-project for shared instruction layout and mcp-setup for MCP registration.

Task guides

<!-- guides:start -->
  • copilot: Copilot sessions and extensions.
  • notifications: Diagnose or change managed turn notifications, brain session-context hooks, and their wiring per host.
  • opencode: OpenCode sessions and provider configuration.
<!-- guides:end -->

Gotchas

  • Edit managed host keys in fmind/dot: on this workstation, Claude, Copilot, and OpenCode settings are merged from modify_* chezmoi templates in ~/.local/share/chezmoi. A direct edit to a managed key (including through /config or a host's settings skill) reverts on chezmoi apply --force; unmanaged keys survive. Change the source, preview with mise run diff (it excludes encrypted targets), then apply.
  • Install vendor skills through the policy: the Copilot and OpenCode guides name each host's sources; install a requested package only through the vendor-skill policy and retain the existing package manager's ownership.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.