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/rgotify/claude-mdgit clone --depth 1 https://github.com/dinglebear-ai/rgotifyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/dinglebear-ai/rgotify/claude-md)<a href="https://agentmods.dev/instructions/dinglebear-ai/rgotify/claude-md"><img src="https://agentmods.dev/badge/instructions/dinglebear-ai/rgotify/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.04145 | $0.04145 |
| Opus 5 | $0.02073 | $0.02073 |
| Sonnet 5 | $0.00829 | $0.00829 |
| Haiku 4.5 | $0.00415 | $0.00415 |
Grade A, and why
rgotify CLAUDE.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 3d 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.
- 3d ago First seen · 300 lines · 4,145 tokens per session scan A a5907051f247
rgotify CLAUDE.md is an instructions file published in the GitHub repository dinglebear-ai/rgotify (2 stars, last pushed 9d ago), licensed AGPL-3.0. It adds 4,145 tokens to every session, about $0.0207 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
cortex CLAUDE.md
Claude Code instructions for dinglebear-ai/cortex, covering claude.md — cortex, repo facts, commands, architecture and ports.
runifi CLAUDE.md
Claude Code instructions for dinglebear-ai/runifi, covering unifi-rmcp — claude.md, repo facts, the controller, module map and action surface.
cortex AGENTS.md
AGENTS.md instructions for dinglebear-ai/cortex, a project described as: Rust MCP/HTTP log aggregation platform for homelab syslog, Docker logs, OTLP ingest, SQLite/FTS search, and AI transcript correlation.
cortex GEMINI.md
Gemini CLI instructions for dinglebear-ai/cortex, a project described as: Rust MCP/HTTP log aggregation platform for homelab syslog, Docker logs, OTLP ingest, SQLite/FTS search, and AI transcript correlation.
runifi AGENTS.md
AGENTS.md instructions for dinglebear-ai/runifi, a project described as: Rust MCP server and CLI for UniFi Network controllers, exposing REST-backed network operations through MCP, CLI, auth, and plugin packaging.
runifi GEMINI.md
Gemini CLI instructions for dinglebear-ai/runifi, a project described as: Rust MCP server and CLI for UniFi Network controllers, exposing REST-backed network operations through MCP, CLI, auth, and plugin packaging.