What is rules_agents AGENTS.md?

Repository instructions for rules_agents, a Bazel-based tool that defines and installs coding-agent skills, profiles, and runners within a repository. Bazel is a build and automation system.

Use them when working on rules_agents features, tests, documentation, validation, setup, manifests, or local agent installation.

They give agents one source of truth for the repository's scope, supported clients, constraints, and commands, reducing assumptions during development.

How jastice/rules_agents configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to jastice/rules_agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jastice/rules_agents/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jastice/rules_agents

Made for: Codex, OpenCode.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/jastice/rules_agents/agents-md/github.svg)](https://agentmods.dev/instructions/jastice/rules_agents/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/jastice/rules_agents/agents-md"><img src="https://agentmods.dev/badge/instructions/jastice/rules_agents/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/jastice/rules_agents/agents-md"><img src="https://agentmods.dev/badge/instructions/jastice/rules_agents/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,959 This file is loaded in full into every session.

When invoked 1,959 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01959	$0.01959
Opus 5.5	$0.00784	$0.00784
Sonnet 5.5	$0.00392	$0.00392
Haiku 4.5	$0.00196	$0.00196

Measured 2mo ago against content hash 72034ce0cdc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rules_agents 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 2mo 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 · 197 lines

How it starts

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

This file applies to the entire repository.

What This Repo Is

rules_agents is a Bazel-based repo-scoped agent environment tool.

Current implemented scope:

supported agent clients: codex, claude_code, pi
local skills declared in Bazel with agent_skill(...)
remote skills synthesized from git archive downloads with skill_deps.remote(...)
profile artifacts declared with agent_profile(...)
concrete runners declared with agent_runner(...)
repo-local installation into native agent directories
validation and launch flows through doctor, manifest, setup, and run

Non-goals:

general agent orchestration
global user config management
agent binary installation
secret storage or secret minting

Source Of Truth

Treat current code, tests, and repository docs as the source of truth.
Treat everything under spec/ as historical reference unless the user explicitly says to adopt or follow a spec document.
If a task explicitly references a spec doc, use only the relevant sections and say that the spec is being treated as design input for that task.

Current Public Surface

The public Bazel API today is:

agent_skill
agent_profile
agent_runner
skill_deps

Current behavior:

agent_skill(...) packages one portable skill bundle rooted at SKILL.md
agent_profile(...) builds a reusable profile artifact and :name_manifest
agent_runner(...) realizes a profile for one client and generates :name, :name_setup, :name_run, :name_doctor, and :name_manifest
skill_deps.remote(...) synthesizes remote agent_skill targets from archive contents
skill_deps.registries(...) enables registry discovery, not installation by itself

Do not describe this repo as only exposing agent_skill, agent_profile, and skill_deps. agent_runner is part of the implemented public surface.

Core Constraints

Keep the implementation narrow and boring:

install Codex skills under .agents/skills
install Claude Code skills under .claude/skills
install Pi skills under .pi/skills
support Linux and macOS; do not claim Windows support unless the code, docs, and tests are updated together
rely on normal repository-root discovery for both clients
do not depend on CODEX_HOME for Codex skill installation
do not synthesize a global Claude home
keep generated file ownership limited to tool-managed subdirectories
preserve machine-readable manifest and doctor outputs

Read the full file on GitHub · 197 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.

2mo ago First seen · 197 lines · 1,959 tokens per session scan A 72034ce0cdc6

Subscribe to this mod's changes

rules_agents AGENTS.md is an instructions file published in the GitHub repository jastice/rules_agents (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,959 tokens to every session, about $0.0078 per session on Opus 5.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-31.

Building agents agent agentic-ai bazel bazel-rules

rules_agents AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rules_agents AGENTS.mdjastice/rules_agents	Instructions file	5	5mo ago	Apache-2.0	A	1,959	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	2d ago	MIT	A	4,313	Codex, OpenCode

rules_agents: Instructions file for Codex