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/canner/wren-engine/agents-mdgit clone --depth 1 https://github.com/Canner/wren-engineWhat 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.00145 | $0.00145 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
wren-engine 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.
This is a copy
94% identical to clickhouse-go AGENTS.md — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AGENTS.md
All project instructions live in .claude/CLAUDE.md. Please refer to that file for repository overview, build commands, architecture, and conventions.
Each module also has its own .claude/CLAUDE.md with module-specific guidance:
wren-core/.claude/CLAUDE.mdwren-core-base/.claude/CLAUDE.mdwren-core-py/.claude/CLAUDE.mdibis-server/.claude/CLAUDE.mdmcp-server/.claude/CLAUDE.mdwren-core-legacy/.claude/CLAUDE.md
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.
- 2d ago First seen · 13 lines · 145 tokens per session scan A 0af183a0f797
wren-engine AGENTS.md is an instructions file published in the GitHub repository Canner/wren-engine (663 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 145 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to clickhouse-go AGENTS.md, differing in 14 lines, and is treated as a copy.
Other instructions, from other repositories
lightdash CLAUDE.md
Claude Code instructions for lightdash/lightdash, covering claude.md, agent skills, issue tracker, triage labels and domain docs.
publisher AGENTS.md
Instructions for malloydata/publisher, covering working with malloy publisher, what you can do, 1. start the server first, 2. connect your agent and 3. the mcp tools.
publisher CLAUDE.md
Instructions for malloydata/publisher: Copyright (c) Credible Data Inc. SPDX-License-Identifier: MIT -->.
Claude-Code-Promts-Skills CLAUDE.md
Instructions for Rtur2003/Claude-Code-Promts-Skills, covering claude.md, project overview, repository structure, file naming conventions and prompt structure standards.
horizun-pbi-mcp AGENTS.md
AGENTS.md instructions for HorizunGroup/horizun-pbi-mcp, covering repository rules for agents, 1. before touching anything, 2. the mcp contract is untouchable, 3. invariants no phase can break and 4. real data: never enters git.
gem-dota CLAUDE.md
Instructions for whanyu1212/gem-dota, covering claude.md, commands, install project + dev dependencies, run all tests, including slow/integration markers and run a single test file.