agentmako AGENTS.md

Instructions for using Mako, a project-context tool that helps coding agents locate relevant files, symbols, routes, database objects, and known findings. It explains how to combine indexed project information with current files.

In plain words
What is it for?
Use it to ask structural project questions, search current text, investigate routing or database usage, review diagnostics, and check whether project context is fresh.
Why use it?
It helps narrow large codebases before making changes and warns when indexed information may be out of date. This reduces unnecessary searching and missed cross-file effects.

Instructions file for CodexOpenCode

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/drhalto/agentmako/agents-md
Clone the repo
git clone --depth 1 https://github.com/drhalto/agentmako

Made for: Codex, OpenCode.

Per session 2,480 This file is loaded in full into every session.
When invoked 2,480 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.

ModelPer sessionOnce invoked
Fable 5 $0.02480 $0.02480
Opus 5 $0.01240 $0.01240
Sonnet 5 $0.00496 $0.00496
Haiku 4.5 $0.00248 $0.00248

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

Security

Grade A, and why

agentmako 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 2d 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 · 257 lines

How it starts

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

Mako MCP Usage

This file is the short agent-facing guide for projects that have Mako registered as mako-ai:

{
  "mako-ai": {
    "command": "agentmako",
    "args": ["mcp"]
  }
}

In Claude Code, tools usually appear as mcp__mako-ai__<toolName>. Examples below use bare names. For complete CLI/tool details, use agentmako --help, agentmako tool --help, MCP tools/list, or mako_help.

Operating Model

Mako is deterministic project context, not a replacement for reading files, editing carefully, and running tests. Use it to narrow scope: relevant files, symbols, routes, schema objects, findings, freshness, and risks.

Prefer reef_ask before broad grep when the question is about structure, cross-file impact, routing, auth, database usage, diagnostics, or known findings. Prefer live_text_search or shell rg when exact current disk text matters.

Evidence modes:

  • Indexed/Reef: fast and structured, but tied to the last index or persisted fact snapshot.
  • Live: current filesystem or database. Use for exact lines, edited files, or new/generated files.

Read _hints on every Mako result. They are generated from the actual output and often give the best next step.

Default Workflow

Default to reef_ask for project questions. It combines codebase, database, durable findings, diagnostics, instructions, freshness, and quoted literal checks without making the agent manually orchestrate broad tool chains:

{
  "question": "what matters if I change tenant-scoped dashboard role checks?",
  "mode": "plan",
  "focus": ["app/dashboard/layout.tsx"],
  "changedFiles": ["app/dashboard/layout.tsx"]
}

When you need an ordered workflow instead of an answer, call mako_help. It returns a recipe with suggested args and verification steps:

{
  "task": "audit auth flow for tenant-scoped dashboard role checks",
  "focusFiles": ["app/dashboard/layout.tsx"],
  "changedFiles": ["app/dashboard/layout.tsx"]
}

When reef_ask needs raw ranked context expansion, call context_packet:

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

  1. 2d ago First seen · 257 lines · 2,480 tokens per session scan A d9166ca970a9

Subscribe to this mod's changes

agentmako AGENTS.md is an instructions file published in the GitHub repository drhalto/agentmako (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,480 tokens to every session, about $0.0124 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.