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.
npx agentmods add instructions/clawfire/chrome-webhook-extension/claude-mdgit clone --depth 1 https://github.com/clawfire/chrome-webhook-extensionWrote 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/clawfire/chrome-webhook-extension/claude-md)<a href="https://agentmods.dev/instructions/clawfire/chrome-webhook-extension/claude-md"><img src="https://agentmods.dev/badge/instructions/clawfire/chrome-webhook-extension/claude-md.svg" alt="Measured on agentmods" 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 | $0.01326 | $0.01326 |
| Opus 5 | $0.00663 | $0.00663 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
chrome-webhook-extension CLAUDE.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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Chrome extension (Manifest V3) that allows users to manage webhooks and send webpage URLs to registered webhook endpoints via context menus. The extension is designed to integrate with automation workflows like N8N.
Architecture
Core Components
- manifest.json: Chrome extension manifest defining permissions, background scripts, and UI components
- background.js: Service worker handling context menu creation, webhook management, and HTTP requests
- popup.html/popup.js: Extension popup UI for webhook registration and management
- Chrome Storage: Local storage for webhook persistence
Key Features
- Context menu integration for pages, links, and images
- Dynamic webhook menu generation based on stored webhooks
- Data extraction (page titles, link titles, image alt text) before sending to webhooks
- Two-click deletion confirmation for webhook management
Development
Installation for Development
- Load extension in Chrome:
chrome://extensions/→ "Load unpacked" → select project directory - Enable "Developer mode" in Chrome extensions page
Testing
- No automated test framework is configured
- Test manually by:
- Loading extension in Chrome
- Adding webhooks via popup
- Right-clicking on pages/links/images to test context menu functionality
- Verifying webhook payloads are sent correctly
Key Files to Modify
- background.js:1-43: Queue initialization and management
- background.js:45-115: Queue processing with rate limiting
- background.js:184-291: Data extraction and webhook sending
- background.js:303-355: Queue notifications system
- popup.js:51-118: Webhook card creation and rendering
- popup.js:324-358: Form toggle functionality
- popup.js:405-413: Form submission and settings handling
- popup.html:31-420: Modern CSS design system and layout
- manifest.json:6-14: Permissions and host permissions
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.
- 4d ago First seen · 153 lines · 1,326 tokens per session scan A acc627affc1b
chrome-webhook-extension CLAUDE.md is an instructions file published in the GitHub repository clawfire/chrome-webhook-extension (10 stars, last pushed 2mo ago), licensed MIT. It adds 1,326 tokens to every session, about $0.0066 per session on Opus 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
Browser4 CLAUDE.md
Claude Code instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
fix-quera AGENTS.md
Instructions for AlirezaKeshavarz83/fix-quera, covering agent guidance, project shape, visual style, quera page data findings and compatibility findings.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
sendblue-browser-use AGENTS.md
Instructions for sendblue-api/sendblue-browser-use, covering agents.md — sendblue-browser-use, what this repo is, setup, common commands and health (no auth).
sniff AGENTS.md
AGENTS.md instructions for Aboudjem/sniff, covering agents.md: sniff, what this repo is, how an agent should use sniff, handling the playwright setup gate and finding output schema.
browser_oxide AGENTS.md
AGENTS.md instructions for yfedoseev/browser_oxide, covering browseroxide — conventions for ai coding assistants, build & test, architecture, key conventions and where to read more.