What is agent-rules AGENTS.md?

Repository instructions for AI coding agents working on a software project. They point agents to the project’s contribution, release, documentation, development, testing, architecture, and convention files.

Use them before changing code, documentation, workflows, architecture, configuration, or public interfaces, and when preparing contributions or releases.

They prevent agents from missing project-specific rules or relying on outdated duplicated guidance. This helps keep code, documentation, tests, and releases consistent.

agent-rules AGENTS.md — Instructions file by lirantal

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/lirantal/agent-rules/agents-md

Clone the repo

git clone --depth 1 https://github.com/lirantal/agent-rules

Made for: Codex, OpenCode.

Per session 357 This file is loaded in full into every session.

When invoked 357 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00357	$0.00357
Opus 5	$0.00179	$0.00179
Sonnet 5	$0.00071	$0.00071
Haiku 4.5	$0.00036	$0.00036

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

Security

Grade A, and why

agent-rules 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 3d 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.

Origin

This is a copy

100% identical to ls-mcp AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 36 lines

What it actually says

AGENTS.md

Guidance for AI coding agents working in this repository.

Start Here

Before making changes, read:

CONTRIBUTING.md for contribution, PR, testing, commit, and agent-specific expectations.
RELEASE.md for release workflow details.
README.md for user-facing behavior, install/use examples, and package or app overview.
docs/README.md for the project documentation index.
docs/development.md for local setup and development workflows.
docs/testing.md for test strategy, commands, and verification expectations.
docs/architecture.md for project structure, boundaries, and important invariants.
docs/conventions.md for project-specific coding, documentation, and maintenance conventions.

Treat those files as the source of truth. Do not duplicate or reinterpret their rules here.

Documentation

Keep documentation in sync when changing behavior, public interfaces, workflows, architecture, configuration, or operational assumptions.
Put project-specific development details in docs/; keep root files focused on their standard audiences.
Prefer linking to the source of truth over duplicating long instructions across files.
When adding new docs, link them from docs/README.md and update this file only when they become important entry points for future agents.

PRs and Issues

Follow PR, issue, and agent-labeling rules in CONTRIBUTING.md.
Use the issue-linking format specified in CONTRIBUTING.md.

Releases

Follow RELEASE.md for release workflow and changeset creation steps.
If this project uses changesets, treat RELEASE.md and any changeset guidance in CONTRIBUTING.md as authoritative.

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.

3d ago First seen · 36 lines · 357 tokens per session scan A ef27705e3cce

Subscribe to this mod's changes

agent-rules AGENTS.md is an instructions file published in the GitHub repository lirantal/agent-rules (62 stars, last pushed 16d ago), licensed Apache-2.0. It adds 357 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ls-mcp AGENTS.md, differing in 0 lines, and is treated as a copy.

agentic-ai agentic-workflow ai-agents claude-code copilot cursor-ai

backend-pro-max-skill CLAUDE.md

Instructions for shashankswe2020-ux/backend-pro-max-skill, covering claude.md, project overview, search command, useful flags and domains.

shashankswe2020-ux/backend-pro-max-skill · 1,506 tokens

skill-bill AGENTS.md

AGENTS.md instructions for oila-gmbh/skill-bill, covering agents.md, project context, product intent, taxonomy and source and generated files.

oila-gmbh/skill-bill · 2,285 tokens

skill-bill CLAUDE.md

Claude Code instructions for oila-gmbh/skill-bill, a project described as: SkillBill packages your engineering judgment into governed skills, then uses a durable Kotlin runtime to ensure agents actually execute that process consistently, resumably, and with bounded context.

oila-gmbh/skill-bill · 3 tokens

agent-rules AGENTS.md