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.
git clone --depth 1 https://github.com/savedpixel/ai-agent-rules-generatorWrote 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/savedpixel/ai-agent-rules-generator/ratelimitting)<a href="https://agentmods.dev/instructions/savedpixel/ai-agent-rules-generator/ratelimitting"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/ratelimitting/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/savedpixel/ai-agent-rules-generator/ratelimitting"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/ratelimitting.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.00522 | $0.00522 |
| Opus 5.5 | $0.00209 | $0.00209 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
ai-agent-rules-generator ratelimitting.instructions.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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rate Limit Prevention (CRITICAL)
You cannot recover from rate limits - the chat session will stop completely. Prevention is essential. Do NOT ask for confirmation - work autonomously but cautiously.
Rules
- Be concise: Keep responses short and to the point. Avoid verbose explanations.
- Don't repeat back: Don't echo the user's request or repeat code they've already shared.
- Plan first: Before making ANY tool calls, create a complete mental plan. Identify the minimum number of calls needed.
- Absolute minimum tool calls: Only make tool calls that are strictly necessary.
- Batch aggressively: Combine multiple operations into single requests wherever possible.
- Reuse information: Never re-fetch data you already have from earlier in the conversation.
- No exploratory calls: No speculative searches or "just checking" requests.
- Checkpoint silently: After significant work, briefly note what's done so progress isn't lost if the session breaks.
- If uncertain: Make a reasonable decision and proceed - do not ask me to confirm.
- Max 2 tool calls per response: Never make more than 2 tool calls in a single response. Complete the response, then continue in the next one.
Output Length Limits
Responses that are too long will be cut off and fail. Stay within limits.
- Max ~300 lines per response: If output would exceed this, split across multiple responses.
- One file at a time: When generating or editing multiple files, output one file per response, then continue.
- Truncate examples: Show only essential code snippets, not full files unless requested.
- Use summaries: For large changes, summarize what was done instead of showing everything.
- Continue automatically: If you need to split output, end with
... continuingand proceed in the next response without asking.
Visibility
When you take any rate-limit prevention action, output a short status line so I can monitor:
📦 BATCH: [what was combined]- when combining multiple operations♻️ REUSE: [what data]- when reusing data instead of re-fetching⏭️ SKIP: [what was skipped]- when skipping an unnecessary call💾 CHECKPOINT: [progress summary]- when saving progress state✂️ SPLIT: [what's being split]- when breaking output into multiple responses
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.
- 1mo ago First seen · 41 lines · 522 tokens per session scan A f830f5ade197
ai-agent-rules-generator ratelimitting.instructions.md is an instructions file published in the GitHub repository savedpixel/ai-agent-rules-generator (8 stars, last pushed 6mo ago), licensed MIT. It adds 522 tokens to every session, about $0.0021 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.