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.
git clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/lint-fix)<a href="https://agentmods.dev/commands/versoxbt/claude-initial-setup/lint-fix"><img src="https://agentmods.dev/badge/commands/versoxbt/claude-initial-setup/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/versoxbt/claude-initial-setup/lint-fix"><img src="https://agentmods.dev/badge/commands/versoxbt/claude-initial-setup/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.00011 | $0.00517 |
| Opus 5.5 | $0.00004 | $0.00207 |
| Sonnet 5.5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Fix
Run linters and formatters to fix code style issues, then report any remaining manual fixes needed.
Steps
-
Detect the project's lint and format tools:
- Check for ESLint, Prettier, Biome, or similar in the config files and package.json.
- Check for language-specific tools: ruff/black (Python), gofmt (Go), rustfmt (Rust), etc.
- Identify the configuration files (.eslintrc, .prettierrc, biome.json, ruff.toml, etc.).
-
Run the formatter first:
- Execute the formatter with auto-fix (e.g.,
prettier --write .,black .,gofmt -w .). - Capture and note any files that were modified.
- If no formatter is configured, skip this step.
- Execute the formatter with auto-fix (e.g.,
-
Run the linter with auto-fix:
- Execute the linter with fix flag (e.g.,
eslint --fix .,ruff check --fix .). - Capture the output and note auto-fixed issues.
- Record any issues that cannot be auto-fixed.
- Execute the linter with fix flag (e.g.,
-
Review remaining manual issues:
- For each unfixable issue, read the affected code and understand the problem.
- Fix issues that require code logic changes (unused variables, unreachable code, type errors).
- Do not suppress warnings without justification — fix the root cause.
-
Run the linter again:
- Verify all auto-fixed issues are resolved.
- Verify manually fixed issues are resolved.
- Confirm zero lint errors and zero warnings (or only intentionally suppressed warnings).
-
Verify the build:
- Run the build to ensure lint fixes did not break compilation or bundling.
- Run the test suite to ensure lint fixes did not change behavior.
- If anything breaks, revert the problematic fix and apply a different solution.
If the Linter Configuration Is Missing
- Do not introduce a new linter without user approval.
- Note the absence and recommend a linter setup for the project's language.
If Auto-Fix Changes Break Tests
- Revert the auto-fix changes that caused the failure.
- Apply fixes manually with more care for the specific context.
- Run tests after each manual fix.
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.
- 1mo ago First seen · 55 lines · 11 tokens per session scan A 99d503c7273c
lint-fix is a command published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 517 once invoked, about $0.0000 per session on Opus 5.5. 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-31.
Other commands, from other repositories
unity-ralph
Relentless verify-fix loop — refuses to stop until the project is clean. Runs unity-verifier repeatedly with configurable max iterations and stall detection.
unity-doctor
Diagnostic health check — verifies MCP connectivity, .claude/ integrity, Unity project structure, and hook registration.
unity-audit
Full project health check — meta file integrity, missing references, assembly definition graph, code quality scan, scene hierarchy audit.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.
unity-fix
Diagnoses and fixes a Unity bug — reads console errors, checks common causes, applies targeted fix, verifies via MCP.
story-continue
Resume an interrupted story from where you left off.