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 instructions/pdugan20/claudelint/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.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.01071 | $0.01071 |
| Opus 5 | $0.00535 | $0.00535 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
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 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 — 85 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
Auto-Generated Files
Do NOT hand-edit these files — they are overwritten by scripts:
src/rules/index.ts— rule registry (npm run generate:types)src/rules/rule-ids.ts— rule ID union type (npm run generate:types)website/rules/**/*.md— rule documentation pages (npm run docs:generate)website/rules/_sidebar.json— rules sidebar nav (npm run docs:generate)website/data/rule-stats.json— rule count data (npm run docs:generate)CHANGELOG.md— auto-generated by release-it from Conventional Commits
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 · 85 lines · 1,071 tokens per session scan A cd2120548bd2
claudelint AGENTS.md is an instructions file published in the GitHub repository pdugan20/claudelint (12 stars, last pushed today), licensed MIT. It adds 1,071 tokens to every session, about $0.0054 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-30.
Other instructions, from other repositories
oxc AGENTS.md
AGENTS.md instructions for oxc-project/oxc, covering agents.md - ai assistant guide for oxc, ai usage policy for contributors, repository structure, core crates and development commands.
oxc copilot-instructions.md
Copilot instructions for oxc-project/oxc: When reviewing pull requests in this repository.
huly-mcp CLAUDE.md
Claude Code instructions for dearlordylord/huly-mcp, covering project instructions, design principle: llm-first api, project harness (copy to new projects), package manager and verification.
marketing-machine CLAUDE.md
Instructions for cagatayuncu/marketing-machine, covering marketing-machine — contributor notes, commands, architecture in ten lines and invariants (violating these is a bug, not a style choice).
oxc CLAUDE.md
Claude Code instructions for oxc-project/oxc, a project described as: ⚓ A collection of high-performance JavaScript tools.
river-review js-ts.instructions.md
Instructions for s977043/river-review, a project described as: レビューを、組織の判断資産へ。Review Judgment as Code for AI-assisted development — codify your team's review standards as repo-owned skills and run them across the SDLC.