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/alexk-dev/golemcore-bot/agents-mdgit clone --depth 1 https://github.com/alexk-dev/golemcore-botWhat 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.00162 | $0.00162 |
| Opus 5 | $0.00081 | $0.00081 |
| Sonnet 5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
golemcore-bot 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.
What it actually says
Instructions for Codex
- Before starting any task, read
CLAUDE.mdin the repository root and follow it. - If the task touches one or more module directories, also read the matching module-local instruction file(s) before making changes:
golemcore-bot-app/CLAUDE.mdgolemcore-bot-client/CLAUDE.mdgolemcore-bot-contracts/CLAUDE.mddashboard/CLAUDE.md
- If the task spans multiple modules, read all relevant local
CLAUDE.mdfiles. - If rules conflict, the more local file has priority.
- For
dashboard/*,dashboard/CLAUDE.mdtakes precedence.
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 · 12 lines · 162 tokens per session scan A f1974ac8670c
golemcore-bot AGENTS.md is an instructions file published in the GitHub repository alexk-dev/golemcore-bot (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 162 tokens to every session, about $0.0008 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
ai AGENTS.md
AGENTS.md instructions for TanStack/ai, covering agents.md, docs skill (mandatory for claude, grok, and codex), bugfix pr skill (mandatory for claude, grok, and codex), contributing guide (mandatory for issues and prs) and ponytail skill (mandatory for claude, grok, and codex).
hivekeep CLAUDE.md
Instructions for MarlBurroW/hivekeep, covering hivekeep, documentation map, tech stack, key conventions and naming.
LIA-Assistant AGENTS.md
AGENTS.md instructions for jgouviergmail/LIA-Assistant, covering agents.md, project overview, build & development commands, full setup (backend + frontend + git hooks) and stop.
LIA-Assistant CLAUDE.md
Claude Code instructions for jgouviergmail/LIA-Assistant, covering claude.md, project overview, build & development commands, full setup (backend + frontend + git hooks) and stop.
coworker CLAUDE.md
Instructions for Array-Ventures/coworker: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
agent-composer CLAUDE.md
Instructions for mhattingpete/agent-composer, covering agent composer, package managers, development, model provider and key files.