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/task)<a href="https://agentmods.dev/instructions/savedpixel/ai-agent-rules-generator/task"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/task/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/task"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/task.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.01703 | $0.01703 |
| Opus 5.5 | $0.00681 | $0.00681 |
| Sonnet 5.5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
ai-agent-rules-generator task.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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Global Execution Rules
These rules apply to ALL tasks without exception. They are BLOCKING — you may not skip any step.
BLOCKING: Task Lifecycle (execute for EVERY task)
This is a gate-checked pipeline. Each step MUST complete before the next begins. Skipping any step is a rule violation.
Step 1 — BEFORE writing any code
- Add unchecked checkbox item(s) in
docs/task/todo.md - If task is multi-step (≥3 steps), create
docs/task/planning/<task-slug>.mdand reference it in the todo item - For non-trivial requests: write a brief plan before implementation
STOP: Do NOT write implementation code until Step 1 is complete.
Step 2 — During implementation
- Keep progress status accurate in
docs/task/todo.md(check boxes as sub-tasks complete) - If new information invalidates the plan, STOP and re-plan immediately
Step 3 — After implementation, BEFORE marking complete
- Verify the change works (build, dev server, browser, endpoints — whatever applies)
- For UI changes: take screenshot to confirm rendering
- For API changes: test endpoint responses
- For database changes: verify migrations and data integrity
STOP: Do NOT mark the task complete until verification passes.
Step 4 — Log Observations (BLOCKING GATE)
- Follow
.github/instructions/agent-observations.instructions.md - Review everything you touched, read, or discovered during this task
- Append entries to
docs/agent-observations/logs:critical.md,recommendations.md,anomalies.md - If no observations: explicitly state "Observations: none."
STOP: This gate MUST complete before Step 5. Silence is a violation.
Step 5 — Completion (all three are required)
- Remove the finished item from
docs/task/todo.md - Append a row to today's daily task log
docs/task/logs/YYYY-MM-DD.md(see format below) - Update relevant
docs/logic/documentation if the change touches plugin behavior
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 · 181 lines · 1,703 tokens per session scan A 45cc3214b902
ai-agent-rules-generator task.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,703 tokens to every session, about $0.0068 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.
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.
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).