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.
npx agentmods add instructions/cornell-zhang/allo/agents-mdgit clone --depth 1 https://github.com/cornell-zhang/alloWhat 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.00290 | $0.00290 |
| Opus 5 | $0.00145 | $0.00145 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
allo 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.
What it actually says
Building
- Always run
conda activate allobefore building or running tests - Run
pip install -v -e .to build the full project (includes MLIR/C++ backend) - Read
docs/source/dive/frontend_syntax.rstfor comprehensive Allo frontend syntax reference - Read
docs/source/dive/dataflow.rstfor the dataflow programming model (regions, kernels, streams)
Testing
- Run
bash scripts/lint/task_lint.shfor formatting checks - Run
python3 -m pytest --ignore=tests/dataflow tests -vfor tests- Prefer running a single test file instead of the full suite (full suite is slow)
- Use only software simulators (
target="llvm"ortarget="simulator") - If Vitis HLS tests are needed, ask the user to run them manually
Code style
- Make small, targeted diffs rather than large refactors, and always be concise
- Prefer general solutions instead of one-off
if/elsepatches - Place Python frontend code in
allo/ - Place MLIR dialects and passes code in
mlir/ - Add tests and documentation for new features in
tests/anddocs/
Don'ts
- Do not modify repository structure without approval
- Do not install system packages without explicit user confirmation
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 · 24 lines · 290 tokens per session scan A 53e6ca0c1b43
allo AGENTS.md is an instructions file published in the GitHub repository cornell-zhang/allo (408 stars, last pushed 7d ago), licensed Apache-2.0. It adds 290 tokens to every session, about $0.0014 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
livehd AGENTS.md
AGENTS.md instructions for masc-ucsc/livehd, covering agents.md, build & test, key directories, tree library and lhd cli (eprp underneath).
livehd CLAUDE.md
Claude Code instructions for masc-ucsc/livehd: See AGENTS.md — all coding-agent guidance (build/test, sibling repos, contracts, debugging tips) lives there so every agent shares the same doc.
Blaze CLAUDE.md
Claude Code instructions for grloper/Blaze, covering claude.md, what this is, commands, architecture (the big picture) and invariants you must not break.
oxc copilot-instructions.md
Instructions for oxc-project/oxc: When reviewing pull requests in this repository.
compiler-explorer copilot-instructions.md
Instructions for compiler-explorer/compiler-explorer: For each answer to the user, evaluate your level of confidence in the correctness of the answer on a scale from 1 to 10, where 1 is very uncertain and 10 is absolutely certain. If your confidence level is below 8, state so and suggest ways to verify the answer.
liteflow CLAUDE.md
Instructions for dromara/liteflow, covering claude.md, 概述, 命令, 构建 and 构建整个项目(模块集由 jdk 版本自动选择 —— 见下方说明).