ai-dev-skillset: Skill for Claude Code

.agents/skills/quality-lint-format/SKILL.md

quality-lint-format is a skill for Claude Code, Codex from gianverdum/ai-dev-skillset. It costs 196 tokens per session (1,012 once invoked), scanned A, original, MIT.

A required code-quality process that runs the project's linter and formatter after code changes. A linter finds likely code problems, while a formatter keeps code style consistent.

In plain words
What is it for?
Use it whenever code is created, changed, fixed, refactored, or reviewed, before ending the task.
Why use it?
It catches style and quality issues before work is handed over and prevents warnings from being left unresolved.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is gianverdum/ai-dev-skillset's own configuration. It tells Claude Code and Codex how to work on ai-dev-skillset itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-dev-skillset configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gianverdum/ai-dev-skillset. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gianverdum/ai-dev-skillset/main/.agents/skills/quality-lint-format/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/gianverdum/ai-dev-skillset

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 quality-lint-format

README.md
[![agentmods](https://agentmods.dev/badge/skills/gianverdum/ai-dev-skillset/quality-lint-format/github.svg)](https://agentmods.dev/skills/gianverdum/ai-dev-skillset/quality-lint-format)
Your own site
<a href="https://agentmods.dev/skills/gianverdum/ai-dev-skillset/quality-lint-format"><img src="https://agentmods.dev/badge/skills/gianverdum/ai-dev-skillset/quality-lint-format/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 quality-lint-format

Your own site · 80×15
<a href="https://agentmods.dev/skills/gianverdum/ai-dev-skillset/quality-lint-format"><img src="https://agentmods.dev/badge/skills/gianverdum/ai-dev-skillset/quality-lint-format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 196 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,012 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.00196 $0.01012
Opus 5 $0.00098 $0.00506
Sonnet 5 $0.00039 $0.00202
Haiku 4.5 $0.00020 $0.00101

Measured 12d ago against content hash 1660d90f6033, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

quality-lint-format 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 12d 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.

.agents/skills/quality-lint-format/SKILL.md · 49 lines

How it starts

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

Lint e Formatter

Lint e formatter sao ferramentas obrigatorias em todo projeto de software. Use esta skill em qualquer mudanca de codigo.

Regras

  • Todo projeto deve ter um linter idiomatico instalado, configurado e executavel por comando declarado no manifesto da stack (pyproject.toml, package.json, Cargo.toml, go.mod/Makefile, pom.xml/build.gradle, .csproj, composer.json). Se nao existir, instale e configure no escopo da tarefa.
  • Todo projeto deve ter um formatter idiomatico configurado. Quando o linter ja inclui formatador (ruff, biome, gofmt, rustfmt), o linter cobre os dois papeis.
  • O script lint declarado no manifesto deve invocar o linter real, nao ser alias de typecheck, build ou outro comando. Linter e type checker validam coisas diferentes; declare scripts separados quando ambas as ferramentas existirem.
  • Apos qualquer mudanca de codigo, rode lint e formatter localmente. Corrija o que for apontado antes de considerar a tarefa concluida.
  • Trate avisos do linter como erros no fluxo do agente. Nao silencie regras (// eslint-disable, # noqa, #[allow(...)]) para esconder problemas; silencie apenas com justificativa registrada no codigo ou na resposta final.
  • O linter padrao por linguagem esta definido na rule de cada linguagem em .agents/rules. Quando o projeto ja tiver outro linter configurado, preserve-o.

Por que rodar lint sempre

  • Pega bugs latentes: codigo morto, ramos identicos em if/else ou ternario, variavel nao usada, import nao usado, comparacao sempre verdadeira, promise nao aguardada.
  • Pega vicios da linguagem: shadowing, mutacao de parametro, exhaustividade de switch, equality fraca.
  • Fixa estilo: indentacao, ordem de imports, aspas, ponto e virgula. Reduz diff de revisao a sinal real.
  • Padroniza saida de erro entre desenvolvedores e agentes.

Fluxo

  1. Identifique o linter ja usado pelo projeto. Se nao existir, escolha o padrao da linguagem (ver rule da linguagem).
  2. Instale o linter como dependencia de desenvolvimento pelo gerenciador idiomatico (ex.: uv add --dev ruff, yarn add -D eslint @eslint/js typescript-eslint).
  3. Crie ou atualize a configuracao minima do linter no formato esperado pela ferramenta.
  4. Declare scripts no manifesto: pelo menos lint (verificar) e format (aplicar correcoes), separados de typecheck e test.
  5. Rode lint e formatter ao final da mudanca. Corrija os apontamentos.
  6. Documente os comandos no README.md mais proximo quando criar ou alterar a configuracao.

Read the full file on GitHub · 49 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. 12d ago First seen · 49 lines · 0 tokens per session scan A 1660d90f6033

Subscribe to this mod's changes

quality-lint-format is a skill published in the GitHub repository gianverdum/ai-dev-skillset (5 stars, last pushed 2mo ago), licensed MIT. It adds 196 tokens to every session and 1,012 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens