What is swarm-legacy?

Agent settings that run a Ruff check after edited or created files, while allowing common project, Git, GitHub, and Python-tool commands.

Running Ruff after edits, managing branches and commits, inspecting GitHub workflow runs, and installing or building Python project dependencies.

Automatic linting can catch Python style and code problems immediately after changes instead of leaving them until later.

swarm-legacy — Settings file by miopea

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add settings/miopea/swarm-legacy/settings

Clone the repo

git clone --depth 1 https://github.com/miopea/swarm-legacy

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

swarm-legacy scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

"Bash(curl:*)",

.claude/settings.json · 55 lines

What it actually says

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/lint-after-edit.sh",
            "timeout": 10,
            "statusMessage": "Running ruff check..."
          }
        ]
      }
    ]
  },
  "permissions": {
    "allow": [
      "Skill(check)",
      "Skill(commit)",
      "Skill(diagnose)",
      "Skill(fix-and-ship)",
      "Skill(get-latest)",
      "Skill(interview)",

      "Bash(git add:*)",
      "Bash(git branch:*)",
      "Bash(git checkout:*)",
      "Bash(git commit:*)",
      "Bash(git diff:*)",
      "Bash(git fetch:*)",
      "Bash(git log:*)",
      "Bash(git merge:*)",
      "Bash(git push:*)",
      "Bash(git stash:*)",
      "Bash(git status:*)",

      "Bash(gh api:*)",
      "Bash(gh run list:*)",
      "Bash(gh run view:*)",

      "Bash(uv run:*)",
      "Bash(uv sync:*)",
      "Bash(uv build:*)",
      "Bash(uv tool install:*)",
      "Bash(uvx ruff:*)",

      "Bash(curl:*)",
      "Bash(kill:*)",
      "Bash(ls:*)",
      "Bash(sleep:*)"
    ]
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 55 lines scan A 79154ee18ea9

Subscribe to this mod's changes

swarm-legacy is a settings file published in the GitHub repository miopea/swarm-legacy (9 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing ai-agents claude-code orchestrator textual tmux

swarm-legacy

Getting it into your agent

Grade A, and why

Makes network callslowCapability

What it actually says

What this file has done since we first saw it

Other settings, from other repositories

vnx-orchestration

dotfiles

Gold-Band

settings

dotfiles

amux