What is a2ui AGENTS.md?

Repository instructions for the a2ui catalogue project, whose canonical rules are stored in CLAUDE.md. They require declared operations and explicit approval before publishing public artifacts.

Use them when operating on the a2ui catalogue to inspect declared processes, run approved operations, commit changes, or publish only opted-in artifacts.

They prevent ad-hoc deployments, accidental publication, and use of outdated project identifiers.

a2ui AGENTS.md — Instructions file by a2uicatalog

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/a2uicatalog/a2ui/agents-md

Clone the repo

git clone --depth 1 https://github.com/a2uicatalog/a2ui

Made for: Codex, OpenCode.

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

When invoked 797 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.

Model	Per session	Once invoked
Fable 5	$0.00797	$0.00797
Opus 5	$0.00398	$0.00398
Sonnet 5	$0.00159	$0.00159
Haiku 4.5	$0.00080	$0.00080

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

Security

Grade A, and why

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

AGENTS.md · 57 lines

How it starts

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

a2ui-catalogue — Agent Entry Point

This file exists so that ANY coding agent (Gemini, Antigravity, Codex, Claude, …) finds the working rules. The canonical rules live in CLAUDE.md — read it in full before doing anything. project.yaml is the inventory (deployments, script IDs, policy, declared processes); never carry identifiers from conversation memory when the manifest declares them.

Non-negotiables (summary — CLAUDE.md is authoritative)

Every operation goes through a declared process. python3 ops/ops.py list → python3 ops/ops.py run <process>. If the operation you need is not declared, declare it in project.yaml processes: first, then run it. Raw clasp push / clasp deploy or ad-hoc command chains are forbidden — improvisation is the failure mode this system exists to prevent. "ops.py run X or standard clasp push" is not a plan; it is the bug.
Nothing new is published to a2uicatalog.ai or any public surface without explicit per-artifact opt-in from Curtis (policy.published in project.yaml, enforced by tests). Never git add -A. Commits go through python3 ops/ops.py commit "<msg>"; push through ops.py run repo-publish.
Renderer source is ground truth. When atoms/schema.yaml prose and a renderer .gs file disagree about a field shape, the renderer wins (known case: spring_nodes edges are {from, to} node IDs, not the documented {a, b} index pairs).
Verify before shipping: python3 -m pytest tests/ -q. Check ops/log.jsonl before re-diagnosing anything — a previous run may have already recorded it.
Encoded ?p= URLs are emitted by scripts/make_url.py only — never hand-typed or copied between surfaces.
Mutating git commands must name the repo explicitly: git -C <path> add|commit|push. Ambient cwd and a leading cd do not count — the shell cwd resets between calls. Commits and pushes go through the declared processes in rule 2, never raw git.

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

3d ago First seen · 57 lines · 797 tokens per session scan A 12ef3a390f06

Subscribe to this mod's changes

a2ui AGENTS.md is an instructions file published in the GitHub repository a2uicatalog/a2ui (4 stars, last pushed 3d ago), licensed MIT. It adds 797 tokens to every session, about $0.0040 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-31.

a2ui agent agent-skills ai-agents apps-script claude

a2ui AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

a2ui-catalogue — Agent Entry Point

Non-negotiables (summary — CLAUDE.md is authoritative)

What this file has done since we first saw it

Other instructions, from other repositories

ii-agent AGENTS.md

intelligent-terminal rust.instructions.md

InvestSkill GEMINI.md

sortie copilot-instructions.md

crust AGENTS.md

she-love-me CLAUDE.md