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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/samilozturk/agentlint/agents-md"><img src="https://agentmods.dev/badge/instructions/samilozturk/agentlint/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.01560 | $0.01560 |
| Opus 5 | $0.00780 | $0.00780 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
agentlint 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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Lint
Do
- Use repository evidence before editing context artifacts: root scripts, package READMEs, tests, and release docs.
- Keep the monorepo boundary intact:
shared <- core <- mcpandshared <- core <- cli. - Keep strict TypeScript, small published packages, and stderr-only logging.
- Update public docs and docs-consistency tests when CLI commands, MCP tools/resources, or supported clients change.
- Read the package-local AGENTS files before making scoped changes in
packages/mcporpackages/cli.
Do Not
- Do not add
any,console.log, server-side state, or MCP-side file writes. - Do not rename MCP tool/resource IDs or CLI command surface without updating docs and tests in the same change.
- Do not run publish, tag, mirror, or force-history commands unless the user explicitly asks.
- Do not duplicate README prose here; keep this file operational.
Repository Evidence
- Public npm packages:
@agent-lint/mcpand@agent-lint/cli. - Authoritative MCP surface:
packages/mcp/src/catalog.tsandpackages/mcp/src/tools/. - Authoritative CLI surface:
packages/cli/src/commands/andpackages/cli/src/commands/clients.ts. - Release and packaging rules:
CONTRIBUTING.md,PUBLISH.md,scripts/, and packagepackage.jsonfiles.
Clarification Gate
- Scan code, docs, and tests first.
- Ask only when ambiguity changes the public surface, release behavior, or client config format.
- If repository evidence supports a safe default, proceed without asking.
Quick Commands
pnpm installpnpm run buildpnpm run release-statuspnpm run typecheckpnpm run lintpnpm run testpnpm --filter @agent-lint/mcp run buildpnpm --filter @agent-lint/cli run buildpnpm run mcp:stdiopnpm run cli
Repo Map
packages/shared: schemas, parser, artifact conventions, and shared types.packages/core: guidelines, workspace discovery, quick check, templates, and maintenance snippets.packages/mcp: read-only MCP server, transports, tools, prompts, and resources. Seepackages/mcp/AGENTS.md.packages/cli: TUI commands, client registry, config writers, and maintenance writers. Seepackages/cli/AGENTS.md.scripts/: release, tag, mirror, and verification helpers..cursor/,.windsurf/,.github/copilot-instructions.md,.codex/: client-specific context and config.
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.
- 4d ago First seen · 133 lines · 1,560 tokens per session scan A dc0d7fc1fc43
agentlint AGENTS.md is an instructions file published in the GitHub repository samilozturk/agentlint (30 stars, last pushed 4mo ago), licensed MIT. It adds 1,560 tokens to every session, about $0.0078 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.