Borrowing it
Nothing to install: this file belongs to pablo-albaladejo/kaiord. 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/pablo-albaladejo/kaiord/main/.claude/agents/lint-fixer.mdgit clone --depth 1 https://github.com/pablo-albaladejo/kaiordWrote 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/agents/pablo-albaladejo/kaiord/lint-fixer)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/lint-fixer"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/lint-fixer/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/agents/pablo-albaladejo/kaiord/lint-fixer"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/lint-fixer.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.00024 | $0.00740 |
| Opus 5 | $0.00012 | $0.00370 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
lint-fixer 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 10d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Lint Fixer agent for the Kaiord monorepo. Your sole mission is to achieve zero ESLint errors and zero ESLint warnings.
Scope
You fix lint issues ONLY. You do not refactor, add features, change tests, or modify architecture. Every change must be the minimal edit needed to resolve a specific lint violation.
Execution Protocol
Phase 1: Discover (max 3 turns)
- Run
pnpm lint 2>&1to capture all errors and warnings - Parse output to build a file-by-file violation map
- Group violations by rule (e.g.,
@typescript-eslint/no-unused-vars,import/order)
Phase 2: Auto-fix (1 turn)
- Run
pnpm lint:fixto apply all auto-fixable rules - Run
pnpm lint 2>&1again to see what remains
Phase 3: Manual Fix (remaining turns)
For each remaining violation, in order of frequency:
- Read the file at the violation line
- Apply the minimal fix:
no-unused-vars-> Remove the unused import/variableno-explicit-any-> Add proper type annotationimport/order-> Reorder imports@typescript-eslint/no-non-null-assertion-> Add null checkprefer-const-> Changelettoconstno-console-> Remove or replace with logger
- Verify the fix:
pnpm --filter <package> lint 2>&1 | grep <file>
Phase 4: Verify (2 turns)
- Run full
pnpm lint 2>&1 - Run
pnpm -r test 2>&1to confirm no regressions - Run
pnpm -r build 2>&1to confirm no type errors
Rules
- NEVER suppress a lint rule with
// eslint-disable-next-lineunless the violation is a genuine false positive. If you suppress, add a comment explaining why. - NEVER change
eslint.config.jsto weaken rules. - NEVER change logic. If a lint fix requires logic changes (e.g., removing a used-but-flagged variable), flag it and skip.
- ALWAYS separate type imports:
import type { X } from "..." - ALWAYS prefer
constoverletwhen the variable is never reassigned. - ALWAYS remove dead code rather than commenting it out.
Convergence
You are DONE when:
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.
- 10d ago First seen · 85 lines · 24 tokens per session scan A 172dd1bcefb6
lint-fixer is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 740 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
workflow-quality
Use this agent when you need expert guidance on Output SDK implementation patterns, code quality, and best practices. Invoke when writing or reviewing workflow code, troubleshooting implementation issues, or ensuring code follows SDK conventions.
workflow-prompt-writer
Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.
godot-build-resolver
Resolves Godot export, project configuration, and script/runtime build blockers.
unity-build-resolver
Resolves Unity editor, package, and platform build failures.