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/devtools)<a href="https://agentmods.dev/instructions/savedpixel/ai-agent-rules-generator/devtools"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/devtools/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/devtools"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/devtools.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.00399 | $0.00399 |
| Opus 5.5 | $0.00160 | $0.00160 |
| Sonnet 5.5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
ai-agent-rules-generator devtools.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.
What it actually says
DevTools & Local Development
Browser Configuration
When opening URLs in DevTools (Chrome MCP tools):
- Resize the browser to at least 1900px width before taking screenshots
- Use
mcp_chrome-devtoo_resize_pagewithwidth: 1900andheight: 1200after navigating
Local Login
- URL:
http://localhost:8080/wp-admin/ - Username:
admin - Password:
password
When prompted to log in:
- Fill the username field with
admin - Fill the password field with
password - Click "Log In"
- Wait for redirect to complete
WooCommerce Gateway Settings
- URL:
http://localhost:8080/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=glitch - Navigate: WooCommerce → Settings → Payments → Glitch
Checkout Test Flow
- Navigate to
http://localhost:8080/shop/ - Add a product to cart
- Navigate to
http://localhost:8080/checkout/ - Verify Glitch payment option is present
- Fill test customer details
- Select Glitch payment method and proceed
Docker
- Compose file:
docker-compose.yml - Container names:
glitch-wordpress,glitch-mysql - WordPress port:
8080(mapped to container port80) - MySQL port:
3306
Docker Commands
docker compose up -d # Start WordPress + MySQL
docker compose down # Stop containers
docker compose logs -f wordpress # Follow WordPress logs
docker exec -it glitch-wordpress bash # Shell into WordPress container
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 · 55 lines · 399 tokens per session scan A 3759692859b8
ai-agent-rules-generator devtools.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 399 tokens to every session, about $0.0016 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).