Borrowing it
Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/lint_fix.mdgit clone --depth 1 https://github.com/swarm-ai-research/swarmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/swarm-ai-research/swarm/lint_fix)<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/lint_fix"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/lint_fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/lint_fix"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/lint_fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00433 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
lint_fix scanned grade A with 0 findings 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/lint-fix
Run ruff auto-fix on a directory after multi-file creation, then report remaining issues. Fills the gap between "just wrote code" and "ready to stage."
Usage
/lint-fix <path> [--test]
Examples:
/lint-fix swarm/bridges/live_swe//lint-fix swarm/research/ --test
Behavior
-
Run
ruff check --fix <path>. Report what was auto-fixed (import sorting, unused imports, etc.). -
Re-run
ruff check <path>. Report any remaining unfixable issues. -
If
--testflag is given, detect and run the associated test file:- For
swarm/bridges/foo/, look fortests/test_foo_bridge.pyortests/test_foo.py - For
swarm/core/foo.py, look fortests/test_foo.py - Run
python -m pytest <test_file> -v
- For
-
Print a summary:
Lint-Fix Results
─────────────────────────────
Auto-fixed: N issues (import sort, unused imports, ...)
Remaining: M issues (or "clean")
Tests: PASS / FAIL / SKIP (if --test)
─────────────────────────────
Why this exists
After creating multiple files, ruff consistently finds trivially fixable issues (F401 unused imports, I001 import sorting, F841 unused variables). Running ruff check --fix first, then checking for remaining issues, collapses a 4-step manual cycle (lint → edit → lint → edit) into one command.
This pattern appeared in 2 consecutive sessions and errored both times.
Difference from /preflight
/preflight operates on staged files and mirrors the pre-commit hook. /lint-fix operates on unstaged/new files immediately after creation, before staging. Use /lint-fix right after writing code, then /preflight after staging.
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.
- 9d ago First seen · 43 lines · 0 tokens per session scan A 375be97fef0b
lint_fix is a command published in the GitHub repository swarm-ai-research/swarm (42 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
debug
Systematic 9-step debugging framework. Generate 20+ hypotheses, rank by likelihood, implement most probable fix.
css-debug
Debug CSS issues including specificity conflicts, cascade problems, and layout bugs.
performance-optimization
Optimize application performance end-to-end using specialized performance and optimization agents.