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/doc-sync)<a href="https://agentmods.dev/instructions/savedpixel/ai-agent-rules-generator/doc-sync"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/doc-sync/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/doc-sync"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/doc-sync.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.01652 | $0.01652 |
| Opus 5.5 | $0.00661 | $0.00661 |
| Sonnet 5.5 | $0.00330 | $0.00330 |
| Haiku 4.5 | $0.00165 | $0.00165 |
Grade A, and why
ai-agent-rules-generator doc-sync.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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Sync Rules
These rules apply when modifying files under includes/. They define which documentation to update and when.
MANDATORY: Auto-Update Documentation
Whenever you implement changes, you MUST update the relevant documentation files. Never skip this step. If you are unsure which docs to update, consult the Documentation Trigger Map below and ask the user if needed — do not skip doc updates because you're uncertain. Only the user may waive documentation requirements.
Documentation Timing Gate (BLOCKING — requires user verification first)
You may NOT update documentation, update task logs, or perform any batch-boundary step until ALL of the following gates have passed in order:
- Agent Self-Evaluation Gate — You confirmed this is the best solution (see
task.instructions.md→ Agent Self-Evaluation Gate). - Visual Verification Gate — If the work affects front-end/UI/visual elements, you opened a browser, took screenshots, and visually confirmed (see
task.instructions.md→ Visual Verification Gate). HTML inspection, DOM queries, andcurldo NOT count. - User Verification Gate — The user has either tested and confirmed, OR explicitly waived testing (see
task.instructions.md→ User Verification Gate).
If the user has not yet responded to the verification prompt, you may NOT:
- Edit any file in
docs/ - Edit any file in
docs/task/logs/ - Edit any file in
docs/agent-observations/ - Stage, commit, or push any changes
Scenario Evidence Requirement (BLOCKING): Documentation is blocked until all required behavior-path scenarios were executed end-to-end.
Untested Disclosure Requirement (BLOCKING): The verification summary must include an explicit Not Tested section listing every unexecuted check/scenario (or Not Tested: none).
CRITICAL — NO SKIPPING: You are never permitted to bypass this timing gate on your own judgment.
Update "Last updated" Date on Every Doc Edit
Whenever you edit any markdown file in docs/, you MUST also update its > **Last updated:** YYYY-MM-DD line (or <!-- Updated: YYYY-MM-DD --> comment) to today's date.
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 · 196 lines · 1,652 tokens per session scan A e1d17bff9a21
ai-agent-rules-generator doc-sync.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 1,652 tokens to every session, about $0.0066 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.