auto-cr AGENTS.md

A set of instructions for AI agents working in the auto-cr repository. auto-cr is a JavaScript and TypeScript tool that scans code and applies or reports custom rules.

In plain words
What is it for?
Use it when running auto-cr, choosing text or JSON output, scanning JavaScript or TypeScript files, configuring custom rules, or interpreting exit codes.
Why use it?
It documents the repository layout, command-line options, supported files, configuration, ignore files, and output behavior in one place.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/wangweiwei/auto-cr/agents-md
Clone the repo
git clone --depth 1 https://github.com/wangweiwei/auto-cr

Made for: Codex, OpenCode.

Per session 769 This file is loaded in full into every session.
When invoked 769 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00769 $0.00769
Opus 5 $0.00385 $0.00385
Sonnet 5 $0.00154 $0.00154
Haiku 4.5 $0.00077 $0.00077

Measured 2d ago against content hash 1a435a380abc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auto-cr 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 2d 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.

AGENTS.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS

This file is for AI agents and automation working in this repo. Keep human-facing content in README.md for readability and SEO.

AI Metadata

project: auto-cr
repo: https://github.com/wangweiwei/auto-cr
packages:
  - auto-cr-cmd
  - auto-cr-rules
languages: [JavaScript, TypeScript]
cli: "npx auto-cr-cmd --language en <path>"
outputs: [text, json]
config_files: [.autocrrc.json, .autocrrc.js]
ignore_files: [.autocrignore.json, .autocrignore.js]

CLI Behavior (structured)

cli_options:
  - flag: --language
    values: [zh, en]
    default: LANG env (fallback zh)
  - flag: --output
    values: [text, json]
    default: text
  - flag: --progress
    values: [tty-only, yes, no]
    default: no
  - flag: --stdin
    note: "reads when piped; supports newline or NUL separators"
  - flag: --rule-dir
  - flag: --config
  - flag: --ignore-path
  - flag: --tsconfig
scan:
  extensions: [.ts, .tsx, .js, .jsx]
  skip_dts: true
  directory_scan_skips: [node_modules]
  stdin_auto_read_when_piped: true
output:
  text: stderr
  json: stdout
exit_codes:
  ok: 0
  errors_or_fatal: 1
custom_rules:
  extensions: [.js, .cjs, .mjs]
  exports: [rule, rules, default, array]
env:
  AUTO_CR_WORKERS: "0/1 single-thread; >1 sets worker count; default CPU-1 when files >= 20"

Repo Layout

  • packages/auto-cr-cmd: CLI implementation (entry: packages/auto-cr-cmd/src/index.ts).
  • packages/auto-cr-rules: Rule SDK + built-in rules (rules in packages/auto-cr-rules/src/rules, messages in packages/auto-cr-rules/src/messages.ts).
  • docs/: Configuration + rule docs.
  • examples/: Example projects and rule demos.
  • scripts/: Workspace utilities, including README syncing.

Common Commands

  • Install deps: pnpm install (workspace uses [email protected]).
  • Build all: pnpm run build
  • Build all (force): pnpm run build:force
  • Dev/watch CLI: pnpm run dev
  • Run CLI in TS: pnpm run cli

User-Facing Config

  • .autocrrc.json / .autocrrc.js for rule settings (see docs/config.md).
  • .autocrignore.json / .autocrignore.js for ignore patterns (see docs/config.md).
  • tsconfig.json is used to infer parser options; override with --tsconfig.

Read the full file on GitHub · 84 lines

Changes

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.

  1. 2d ago First seen · 84 lines · 769 tokens per session scan A 1a435a380abc

Subscribe to this mod's changes

auto-cr AGENTS.md is an instructions file published in the GitHub repository wangweiwei/auto-cr (20 stars, last pushed 5d ago), licensed MIT. It adds 769 tokens to every session, about $0.0038 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens