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/thinkex-oss/thinkex/agents-mdgit clone --depth 1 https://github.com/ThinkEx-OSS/thinkexWhat 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.00166 | $0.00166 |
| Opus 5 | $0.00083 | $0.00083 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
thinkex 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
Agent notes
- Early-stage repo with effectively no users: treat changes as greenfield. No legacy shims, no back-compat paths, and no data migrations for existing rows unless explicitly requested. Prefer deleting superseded code over keeping it reachable.
- Merging IS shipping: Cloudflare Workers Builds auto-deploys every push to
mainto production (wrangler migrations included). Thestagingbranch deploys to the staging env the same way. There is no manual deploy step. - Commits carry code and the docs that ship with it. Research notes, analysis
writeups, and other non-shipping generated markdown (e.g.
docs/research/) stay as untracked working files — commit them only when explicitly asked.
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 · 166 tokens per session scan A cd0dd99ee927
thinkex AGENTS.md is an instructions file published in the GitHub repository ThinkEx-OSS/thinkex (55 stars, last pushed 8d ago), licensed MIT. It adds 166 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
siyuan AGENTS.md
AGENTS.md instructions for siyuan-note/siyuan, covering agents.md, 1. non-negotiable constraints, do not hand-edit, verification and prohibited operations and 2. project-specific rules.
obsidian-mcp-server AGENTS.md
Instructions for cyanheads/obsidian-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool — obsidianlisttags.
edgeever AGENTS.md
AGENTS.md instructions for tianma-if/edgeever, covering agents.md, 文档与分支约束, github actions 与 release 约束及流程, 🇨🇳 中文说明 / chinese changelog and 主要更新.
hippocampus CLAUDE.md
Instructions for sturlese/hippocampus, covering layout, frontmatter schema, conventions, answering questions from the vault (read order) and contradictions.
hippocampus AGENTS.md
Instructions for sturlese/hippocampus: Read and follow CLAUDE.md in the repository root completely before doing any work. It is the canonical project contract, written for Claude Code as the native host; its vault rules and workflows apply unchanged to Codex.
NoteMeld AGENTS.md
Instructions for Hehejie1/NoteMeld, covering agents.md, 必读文档, 必须搜索现状, 禁止事项 and change spec 规则.