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/browsetools)<a href="https://agentmods.dev/instructions/savedpixel/ai-agent-rules-generator/browsetools"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/browsetools/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/browsetools"><img src="https://agentmods.dev/badge/instructions/savedpixel/ai-agent-rules-generator/browsetools.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.00490 | $0.00490 |
| Opus 5.5 | $0.00196 | $0.00196 |
| Sonnet 5.5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
ai-agent-rules-generator browsetools.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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTools Verification Rules
MANDATORY: Browser Verification Before Completion
After every new feature, bug fix, or change that touches the UI or frontend behavior, you MUST verify the change works using Chrome DevTools MCP tools before marking it as complete.
Required Verification Steps
- Visual verification — Use
take_screenshotto confirm the page renders correctly. - Console check — Use
list_console_messagesto confirm there are no JS console errors. - Functional test — Use
click,fill, and other interaction tools to test the changed behavior end-to-end. - State check — Use
evaluate_scriptto inspect DOM values or framework state when needed. - Regression check — Take screenshots of adjacent/related views to ensure no regressions.
Completion Gate
- Only after successful verification may you mark the task as completed.
- If verification fails, fix the issue and re-verify before completing.
- Do NOT mark any UI task as done until it has been tested and confirmed working.
Dev Server Prerequisite
Before browser verification, ensure the WordPress dev environment is running:
cd /path/to/glitch-woocommerce-gateway && wp-env start
The WordPress admin runs at http://localhost:8888/wp-admin/. The storefront runs at http://localhost:8888/. Navigate to the relevant page before taking screenshots or interacting.
Do not kill the server after you finished browsing, keep it alive so that the user can still work on it.
Key Pages for Verification
- Admin Settings:
http://localhost:8888/wp-admin/admin.php?page=wc-settings&tab=checkout§ion=glitch_gateway - Checkout Page:
http://localhost:8888/checkout/ - Order Admin:
http://localhost:8888/wp-admin/edit.php?post_type=shop_order
Authentication Credentials
The WordPress dev environment requires login before accessing admin pages. Use these credentials:
- Username:
admin - Password:
password
After navigating to any admin URL, if redirected to a login page, fill in the credentials above and submit before proceeding with verification.
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 · 52 lines · 490 tokens per session scan A 854debc5814d
ai-agent-rules-generator browsetools.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 490 tokens to every session, about $0.0020 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.