agentleFS
zaxbysaucezaxbysauce/opencode-swarm/.agents/skills/unswarm/SKILL.md

unswarm

Skill517 starsChanged 3 days agoMITView on GitHub

Codex adapter for disabling a previously requested swarm-like workflow in the current thread. Use when the user says unswarm, stop swarm mode, return to normal mode, simplify the workflow, or stop using extra review/delegation rigor.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .claude/skills/unswarm/SKILL.md only if you need the original Claude command semantics.

    line 10
  2. Very specific:

    Stop applying $swarm or $swarm-implement as an ongoing workflow posture unless the user explicitly asks for it again.

    line 14
  3. Distinctive:

    Keep following repository instructions, safety rules, and any task-specific skills that still apply.

    line 15
  4. Distinctive:

    Prefer direct execution and concise updates over extra planning/review layers.

    line 16
  5. Distinctive:

    Do not make file changes solely to "disable" swarm mode.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Unswarm

Read .claude/skills/unswarm/SKILL.md only if you need the original Claude command semantics.

For Codex, this skill means:

  • Stop applying $swarm or $swarm-implement as an ongoing workflow posture unless the user explicitly asks for it again.
  • Keep following repository instructions, safety rules, and any task-specific skills that still apply.
  • Prefer direct execution and concise updates over extra planning/review layers.
  • Do not make file changes solely to "disable" swarm mode.

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.