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/dinglebear-ai/dendrite/agents-mdgit clone --depth 1 https://github.com/dinglebear-ai/dendriteWhat 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.00004 | $0.00004 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
dendrite 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 1 lines · 4 tokens per session scan A 6ebdb617a810
dendrite AGENTS.md is an instructions file published in the GitHub repository dinglebear-ai/dendrite (1 stars, last pushed 6d ago), licensed AGPL-3.0. It adds 4 tokens to every session, about $0.0000 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
obsidian-agent-client AGENTS.md
AGENTS.md instructions for RAIT-09/obsidian-agent-client, covering agent client plugin - llm developer guide, architecture, data flow, acp event flow (single path) and permission flow.
memex GEMINI.md
Instructions for STiFLeR7/memex, covering memex, agent instructions, execution mode, non-negotiables and what is in scope.
kmux AGENTS.md
Instructions for kkd927/kmux, covering agents.md, kmux focus and test discipline.
obsidian-llm-hub AGENTS.md
Instructions for takeshy/obsidian-llm-hub, a project described as: Obsidian plugin for AI chat, workflow automation, and semantic search — supports Gemini, OpenAI, OpenRouter, Grok, Ollama, and CLI backends.
docker-gemini-cli GEMINI.md
Instructions for naoyoshinori/docker-gemini-cli, covering 1. core functionality, 2. project structure and key files, 2.1. image variants, 2.2. automation and 3. documentation.
gemini-faf-mcp GEMINI.md
Instructions for Wolfe-Jam/gemini-faf-mcp, covering gemini.md — gemini-faf-mcp, test & verify, where things live, stack and before changing things.