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/travisennis/acai/agents-mdgit clone --depth 1 https://github.com/travisennis/acaiWrote 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.
[](https://agentmods.dev/instructions/travisennis/acai/agents-md)<a href="https://agentmods.dev/instructions/travisennis/acai/agents-md"><img src="https://agentmods.dev/badge/instructions/travisennis/acai/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.01769 | $0.01769 |
| Opus 5 | $0.00885 | $0.00885 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
acai 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Project
Acai is a TypeScript/Node.js CLI assistant for coding workflows, available as both one-shot CLI and interactive REPL/TUI. It integrates model providers, agent-callable tools, skills, dynamic tools, and persisted sessions.
Compatibility surfaces: CLI flags and commands, REPL/TUI output, prompt and AGENTS.md loading, project configuration, environment variables, dynamic tool and skill contracts, provider and model IDs, tool schemas, session and log formats, filesystem and shell permission boundaries, terminal rendering, package entry points, the supported Node.js range, and documented output formats. Preserve them unless explicitly changed.
Operating Loop
- Do managed-work intake first. If the request is about a task, ExecPlan, ADR, or research note, use
ahm(see Managed Work Intake Withahm) to understand that work item before choosing implementation docs. If the request is directly about code, CLI behavior, tests, docs, build, release, or repo mechanics, skipahmintake and classify it directly. - Classify the concrete request before editing.
- Load only the routed docs needed for that request.
- Preserve compatibility surfaces unless explicitly changed.
- Keep edits surgical and verify according to risk.
- After implementation edits, run a review in a subagent and address findings until none remain, then perform preflight. If a third round reports findings of the same class, stop patching: report the finding class and the suspected design flaw, and escalate to a design decision.
- State the selected route and loaded docs, then handoff with changes, checks, and remaining risk.
When this file conflicts with a specialized workflow doc for that workflow, the specialized doc wins. Keep AGENTS.md as routing, not as a command catalog or procedure manual.
Workflow Routing
CLI, REPL, TUI, And User Output
Use for command parsing, slash commands, stdin, interactive behavior, terminal rendering, markdown, autocomplete, and user-visible text.
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 · 158 lines · 1,769 tokens per session scan A f2958da832f3
acai AGENTS.md is an instructions file published in the GitHub repository travisennis/acai (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,769 tokens to every session, about $0.0088 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.
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).
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.
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.
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.
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).
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.