linter-loop-limits

linter-loop-limits is a skill for Claude Code, Codex from adilkalam/orca. It costs 42 tokens per session (1,189 once invoked), scanned A, original, MIT.

A rule for limiting repeated attempts to fix the same linter error to three tries before asking the user for help.

In plain words
What is it for?
Use it when automating lint checks and handling errors that remain after several targeted fixes.
Why use it?
It prevents coding agents from getting stuck in endless repair loops or making more changes without understanding the cause.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when automating lint checks and handling errors that remain after several targeted fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adilkalam/orca/linter-loop-limits
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.

Any agent
npx skills add adilkalam/orca --skill linter-loop-limits
Clone the repo
git clone --depth 1 https://github.com/adilkalam/orca

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for linter-loop-limits

README.md
[![agentmods](https://agentmods.dev/badge/skills/adilkalam/orca/linter-loop-limits/github.svg)](https://agentmods.dev/skills/adilkalam/orca/linter-loop-limits)
Your own site
<a href="https://agentmods.dev/skills/adilkalam/orca/linter-loop-limits"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/linter-loop-limits/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.

agentmods 80×15 button for linter-loop-limits

Your own site · 80×15
<a href="https://agentmods.dev/skills/adilkalam/orca/linter-loop-limits"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/linter-loop-limits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01189
Opus 5.5 $0.00017 $0.00476
Sonnet 5.5 $0.00008 $0.00238
Haiku 4.5 $0.00004 $0.00119

Measured 1mo ago against content hash b2388cdbe919, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

linter-loop-limits 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.

skills/linter-loop-limits/SKILL.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Linter Loop Limits

RULE: Do NOT loop more than 3 times fixing linter errors on the same file.

The Problem

Agents can get stuck in infinite loops trying to fix linter errors, wasting tokens and time without making progress. Each failed attempt often introduces new issues or reverts previous fixes.

The 3-Strike Rule

Strike 1: Initial Fix

  • Read the linter error carefully
  • Understand what the rule is checking
  • Make targeted fix based on error message
  • Run linter again

Strike 2: Second Attempt

  • If first fix didn't work, analyze WHY
  • Consider if the error message is misleading
  • Check if there are conflicting rules
  • Try a different approach
  • Run linter again

Strike 3: Final Attempt

  • If still failing, step back and reconsider
  • Check if there's a fundamental misunderstanding
  • Review linter configuration
  • Make one more targeted fix
  • Run linter again

After 3 Strikes: STOP

If the error persists after 3 attempts:

DO:

  • STOP trying to fix it automatically
  • Present the error to the user
  • Explain what you've tried
  • Ask for guidance
  • Document the approaches that failed

DON'T:

  • Keep looping hoping it will work
  • Try random fixes
  • Suppress or ignore the error
  • Modify linter config to hide the issue
  • Add eslint-disable comments without permission

Communication Template

After 3 failed attempts, use this format:

I've attempted to fix this linter error 3 times without success:

**Error:** [exact error message]
**File:** [file path and line number]
**Rule:** [linter rule name if available]

**Attempts made:**
1. [First approach] - Result: [what happened]
2. [Second approach] - Result: [what happened]  
3. [Third approach] - Result: [what happened]

**My analysis:** [why it might be failing]

How would you like me to proceed?
- Option A: Try a specific fix you suggest
- Option B: Disable this rule for this line (with eslint-disable)
- Option C: Investigate the root cause further
- Option D: Skip this for now and continue

Read the full file on GitHub · 201 lines

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.

  1. 1mo ago First seen · 201 lines · 42 tokens per session scan A b2388cdbe919

Subscribe to this mod's changes

linter-loop-limits is a skill published in the GitHub repository adilkalam/orca (2 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 1,189 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens