Borrowing it
Nothing to install: this file belongs to pdugan20/claudelint. 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/pdugan20/claudelint/main/AGENTS.mdgit clone --depth 1 https://github.com/pdugan20/claudelintWrote 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/instructions/pdugan20/claudelint/agents-md)<a href="https://agentmods.dev/instructions/pdugan20/claudelint/agents-md"><img src="https://agentmods.dev/badge/instructions/pdugan20/claudelint/agents-md/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/instructions/pdugan20/claudelint/agents-md"><img src="https://agentmods.dev/badge/instructions/pdugan20/claudelint/agents-md.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.01168 | $0.01168 |
| Opus 5.5 | $0.00467 | $0.00467 |
| Sonnet 5.5 | $0.00234 | $0.00234 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
claudelint AGENTS.md 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance
Work modes
- Default to exploration for documentation, design iterations, prototypes, and small changes. Make focused edits directly; do not require a formal spec, separate plan, worktree, or TDD.
- Apply production rigor when the user explicitly asks to ship, harden, prepare a release, or use strict TDD. Match verification to risk and obey any stronger test requirements below.
- Ask before publishing packages, releases, deployments, or other live mutations.
Architecture
This is a single-package repo with three logical components:
- NPM package (
src/,bin/) — TypeScript linter with CLI and programmatic API - Claude plugin (
.claude-plugin/,skills/) — thin wrapper providing skills that call the npm package - Website (
website/) — VitePress documentation site at claudelint.com
See src/AGENTS.md and website/AGENTS.md for component-specific guidance.
Commands
npm run build # Compile TypeScript to dist/
npm run dev # Watch mode
npm test # Jest test suite
npm run lint # All linters in parallel (TS, Vue, CSS, MD, pkg)
npm run lint:fix # Auto-fix all linters
npm run format:check # Prettier check
npm run validate # lint + format + build + test
npm run check:self # Dogfood: build then run claudelint on itself
npm run docs:dev # VitePress dev server (generates rule docs first)
npm run docs:build # Production website build
Code Review Rules
- Flag a new or changed lint rule that lacks focused valid/invalid fixtures, stable rule metadata, generated documentation, and registry/type regeneration.
- Flag hand-edits to generated registries, rule docs, sidebar data, statistics, or the changelog when their documented generator/release source should be changed instead.
- Flag release changes that desynchronize package/plugin/marketplace versions or bypass the documented OIDC trusted-publishing contract.
Auto-Generated Files
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 Changed · +9 lines · +97 tokens per session b1fe499308ba
- 1mo ago First seen · 85 lines · 1,071 tokens per session scan A cd2120548bd2
claudelint AGENTS.md is an instructions file published in the GitHub repository pdugan20/claudelint (14 stars, last pushed yesterday), licensed MIT. It adds 1,168 tokens to every session, about $0.0047 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.