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/ui-design)<a href="https://agentmods.dev/instructions/savedpixel/ai-agent-rules-generator/ui-design"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/ui-design/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/ui-design"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/ui-design.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.00701 | $0.00701 |
| Opus 5.5 | $0.00280 | $0.00280 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
ai-agent-rules-generator ui-design.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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Glitch Payment Gateway — UI Design Instructions
MANDATORY: Follow task.instructions.md
Before starting any UI work, you MUST also follow all rules in .github/instructions/task.instructions.md.
MANDATORY: Read Before Any Admin UI Work
Before writing or modifying any UI element in the WooCommerce admin settings or custom admin views, you MUST read:
docs/plugin/features/3-admin-settings.md— the settings field reference- The matching split doc for the surface you're changing
Strict Rules
-
NEVER invent new CSS classes for admin pages. Use WordPress core admin classes (
form-table,widefat,button,button-primary,notice,notice-success,notice-error, etc.) and WooCommerce settings classes. -
NEVER hardcode colors, spacing, or sizing values. Use WordPress admin CSS custom properties and WooCommerce's existing spacing conventions. Reference
wp-admin/css/common.csspatterns. -
Use the correct button variants:
- Primary action:
button button-primary - Secondary action:
button - Destructive:
button button-link-delete - Small: add
button-small
- Primary action:
-
Use WooCommerce Settings API for all settings fields. Define fields via
init_form_fields()— never render raw HTML form inputs for gateway settings. Valid field types:text,textarea,select,multiselect,checkbox,password,title,decimal. -
Use WordPress notice classes for admin messages:
- Success:
<div class="notice notice-success"><p>...</p></div> - Error:
<div class="notice notice-error"><p>...</p></div> - Warning:
<div class="notice notice-warning"><p>...</p></div> - Info:
<div class="notice notice-info"><p>...</p></div>
- Success:
-
No inline styles. All custom styling goes in
assets/css/glitch-admin.cssand is enqueued viaadmin_enqueue_scripts. -
Use WordPress Dashicons for icons. Reference via
<span class="dashicons dashicons-{name}"></span>. Common ones:dashicons-admin-generic,dashicons-shield,dashicons-warning,dashicons-yes-alt,dashicons-no-alt.
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 · 59 lines · 701 tokens per session scan A 0bb26b861d90
ai-agent-rules-generator ui-design.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 701 tokens to every session, about $0.0028 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.