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.
npx agentmods add skills/luisalima/agent-policy-kit/lintersnpx skills add luisalima/agent-policy-kit --skill lintersgit clone --depth 1 https://github.com/luisalima/agent-policy-kitWrote 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/skills/luisalima/agent-policy-kit/linters)<a href="https://agentmods.dev/skills/luisalima/agent-policy-kit/linters"><img src="https://agentmods.dev/badge/skills/luisalima/agent-policy-kit/linters.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.00544 |
| Opus 5 | $0.00027 | $0.00272 |
| Sonnet 5 | $0.00011 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
linters 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 5d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linters
Add or improve static checks that match the repository's languages, package managers, and existing conventions.
Workflow
- Inspect the project before choosing tools:
- Existing scripts:
package.json,pyproject.toml,Cargo.toml,go.mod,Makefile, CI files, pre-commit config. - Existing formatters, test commands, and dependency managers.
- Languages touched by the current task.
- Existing scripts:
- Prefer existing tooling:
- If a lint command exists, run it and improve configuration only when needed.
- If a nearby package/module already has a linter, mirror that pattern.
- Add the smallest relevant lint setup:
- JavaScript/TypeScript: ESLint or the repo's existing framework lint command.
- Python: Ruff by default, unless the repo already uses Flake8, Pylint, Black, or mypy.
- Go:
gofmt/go vet, andgolangci-lintonly when the repo already expects it or asks for it. - Rust:
cargo fmtandcargo clippy. - Ruby: RuboCop when the repo uses Bundler/Ruby conventions.
- Shell: ShellCheck when shell scripts are part of the repo.
- Wire the linter into the project:
- Add or update a
lintscript, Make target, task runner entry, or CI step that matches existing conventions. - Document the command in
AGENTS.mdonly if agents need to run it regularly.
- Add or update a
- Verify:
- Run the new or updated lint command.
- Fix reported issues only when in scope.
- If lint failures are pre-existing and broad, report them and avoid mixing a large cleanup into unrelated work.
Rules
- Do not add a linter just because one exists for the language. Add it when it protects changed code or a missing project check.
- Do not introduce a new package manager or build system for linting.
- Do not replace an established linter without an explicit reason.
- Do not weaken lint rules to make the current change pass unless the rule is clearly wrong for the project.
- Keep formatter and linter responsibilities separate unless the chosen tool intentionally covers both.
- Prefer a focused follow-up task over broad lint cleanup when failures are unrelated.
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.
- 5d ago First seen · 42 lines · 54 tokens per session scan A 457bedf38bd7
linters is a skill published in the GitHub repository luisalima/agent-policy-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 544 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…