Borrowing it
Nothing to install: this file belongs to 0xmariowu/AgentLint. 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/0xmariowu/AgentLint/main/CLAUDE.mdgit clone --depth 1 https://github.com/0xmariowu/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/0xmariowu/agentlint/claude-md)<a href="https://agentmods.dev/instructions/0xmariowu/agentlint/claude-md"><img src="https://agentmods.dev/badge/instructions/0xmariowu/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.00653 | $0.00653 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
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 8d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentLint
For global rules, see
~/CLAUDE.md. This file contains agent-lint-specific overrides only. Lighthouse for AI-Friendly repos — diagnose, plan, fix.
Local test (run before push)
bash tests/test_compliance.sh && bash tests/test-scanner.sh
Compliance (4 checks, ~1s) + scanner unit tests. Full matrix (multi-OS) runs in CI.
Session Checklist
- If modifying checks → read
standards/evidence.jsonfor evidence backing - If modifying scoring → read
standards/weights.jsonfor weight rationale - If adding a check → must have evidence source (paper, data, or real audit finding)
Rules
- Don't add a check without empirical evidence. Instead, cite: Anthropic data, academic paper, or documented real-world failure. Because: AgentLint's value is evidence-backed recommendations, not opinions.
- Don't hardcode thresholds as pass/fail gates. Instead, measure and compare to reference values. Because: Bitter Lesson — imposing human-defined boundaries creates brittle rules that break when context changes.
- Don't modify scanner output format without updating scorer + plan-generator + reporter. Because: the JSONL schema is a contract between all pipeline stages.
- Don't hardcode paths in skills/*.md. Instead, use
${CLAUDE_PLUGIN_ROOT}to reference bundled files. Because: plugin install path varies per user. - Don't write persistent data to
${CLAUDE_PLUGIN_ROOT}. Instead, use${CLAUDE_PLUGIN_DATA}or~/.al/. Because: plugin root is replaced on update. - When you change a file under
.github/workflows/, also check whethertemplates/universal/<basename>exists and needs the same change. Instead of relying on memory, runbash scripts/lib/check-template-sync.shagainst your staged diff (the pre-commit hook already does this informally) — it counts security-keyword occurrences in both files and warns when they drift. Because: v1.1.9 / v1.1.10 / v1.1.11 each shipped a regression where the in-tree workflow got a security fix but the user-facing template did not, exposing every freshagentlint setuprepo to the same bug.
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.
- 8d ago First seen · 46 lines · 653 tokens per session scan A 8ffef93b92f6
AgentLint CLAUDE.md is an instructions file published in the GitHub repository 0xmariowu/AgentLint (55 stars, last pushed 1mo ago), licensed MIT. It adds 653 tokens to every session, about $0.0033 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
plan-forge powershell.instructions.md
PowerShell best practices for Azure IaC — Az module, script structure, Pester testing, PSScriptAnalyzer.
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).
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).