Borrowing it
Nothing to install: this file belongs to meitalbensinai/rate-limit-monitor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/meitalbensinai/rate-limit-monitor/main/AGENTS.mdgit clone --depth 1 https://github.com/meitalbensinai/rate-limit-monitorWrote 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/meitalbensinai/rate-limit-monitor/agents-md)<a href="https://agentmods.dev/instructions/meitalbensinai/rate-limit-monitor/agents-md"><img src="https://agentmods.dev/badge/instructions/meitalbensinai/rate-limit-monitor/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/meitalbensinai/rate-limit-monitor/agents-md"><img src="https://agentmods.dev/badge/instructions/meitalbensinai/rate-limit-monitor/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00428 | $0.00428 |
| Opus 5 | $0.00214 | $0.00214 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade B, and why
rate-limit-monitor AGENTS.md scanned grade B with 1 finding 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 12d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- backs up `~/.claude/settings.json` (honors `$CLAUDE_CONFIG_DIR`), What it actually says
Install instructions for AI agents
You have been given this repository and asked to install Rate Limit Monitor into the user's Claude Code. Do exactly this:
bash ./install.sh
Then tell the user: "Installed — restart Claude Code to activate it."
That is the whole task. Do not hand-edit settings.json yourself.
What the script does (so you can explain it if asked)
install.sh is safe and idempotent. It:
- verifies
jqis installed (aborts with a clear message if not), - backs up
~/.claude/settings.json(honors$CLAUDE_CONFIG_DIR), - appends the
UserPromptSubmitguard hook without removing existing hooks, - sets the statusline, chaining any statusline the user already has (so their current prompt is preserved),
- re-running it makes no further changes.
Requirements to mention if they fail
jqmust be onPATH(brew install jq/apt-get install -y jq).- The usage data only exists on a paid Claude plan (Pro/Max/Team/Enterprise) and only after the first API response of a session. On API-key/free usage the guard simply never blocks (fails open) — that is expected, not a bug.
Uninstall
bash ./uninstall.sh
Restores the user's original statusline (or removes ours) and drops the guard hook. Also backs up first.
Do NOT
- Do not also run
/plugin installfor this afterinstall.sh— that would wire the guard twice.install.shis the standalone path; the plugin marketplace flow in the README is the alternative for humans who prefer it. - Do not edit the shell scripts unless the user asks; configuration is via env
vars documented in
README.md(RLM_THRESHOLD,RLM_WINDOWS,RLM_OVERRIDE).
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.
- 12d ago First seen · 47 lines · 428 tokens per session scan B f1ec2effa26b
rate-limit-monitor AGENTS.md is an instructions file published in the GitHub repository meitalbensinai/rate-limit-monitor (2 stars, last pushed 2mo ago), licensed MIT. It adds 428 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).