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/samilozturk/agentlint/claude-mdgit clone --depth 1 https://github.com/samilozturk/agentlintWrote 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/samilozturk/agentlint/claude-md)<a href="https://agentmods.dev/instructions/samilozturk/agentlint/claude-md"><img src="https://agentmods.dev/badge/instructions/samilozturk/agentlint/claude-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.1 | $0.01809 | $0.01809 |
| Opus 5 | $0.00905 | $0.00905 |
| Sonnet 5 | $0.00362 | $0.00362 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
agentlint CLAUDE.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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build & Development Commands
pnpm install # install all dependencies
pnpm run build # build all packages (shared → core → mcp → cli, then tsc --build)
pnpm run typecheck # type-check all packages via project references
pnpm run lint # eslint (flat config, ESLint 9+)
pnpm run test # vitest run (all packages)
pnpm run test:watch # vitest in watch mode
Run a single test file:
npx vitest run packages/core/tests/quick-check.test.ts
Run tests matching a pattern:
npx vitest run -t "score"
Run the CLI in dev mode:
pnpm run cli # interactive TUI
pnpm run cli -- scan --stdout # standalone command
Run the MCP server in dev mode:
pnpm run mcp:stdio # stdio transport
pnpm run mcp:inspector # MCP inspector UI
Architecture
Strict TypeScript monorepo with four packages. Dependency flow: shared ← core ← mcp and shared ← core ← cli.
- shared — Types, Zod schemas for MCP tool inputs, artifact conventions (quality metrics, path hints, spec builders), markdown frontmatter parsing (gray-matter).
- core — Pure business logic:
buildGuidelines(),discoverWorkspaceArtifacts(),buildWorkspaceAutofixPlan(),runQuickCheck(),buildMaintenanceSnippet(),scoreArtifact(). Zero state, no LLM, no network, no file writing — read-only analysis returning markdown. - mcp — MCP server wrapping core. Factory:
createAgentLintMcpServer(). Supports stdio (default) and HTTP transports. Registers 5 tools + resources + prompts. All tools use Zod validation,withToolTimeout(), and read-only annotations. - cli — React 19 + Ink terminal UI with Commander.js fallback. Entry logic: TTY + no args → interactive Ink app; args → Commander standalone; no TTY + no args → help text. Commands:
init,scan,prompt,score.
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 · 149 lines · 1,809 tokens per session scan A 256d5551b467
agentlint CLAUDE.md is an instructions file published in the GitHub repository samilozturk/agentlint (30 stars, last pushed 5mo ago), licensed MIT. It adds 1,809 tokens to every session, about $0.0090 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).