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/duyet/google-search-crawler/claude-mdgit clone --depth 1 https://github.com/duyet/google-search-crawlerWrote 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/duyet/google-search-crawler/claude-md)<a href="https://agentmods.dev/instructions/duyet/google-search-crawler/claude-md"><img src="https://agentmods.dev/badge/instructions/duyet/google-search-crawler/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.1 | $0.01792 | $0.01792 |
| Opus 5 | $0.00896 | $0.00896 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
google-search-crawler CLAUDE.md scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **requests** - HTTP client library (cleaner than urllib) How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Google Search Crawler
Project Philosophy
This project embodies the principle that elegant code is inevitable code. Every component, every function, every line exists not because it can, but because it must. We build tools that feel like natural extensions of the developer's mind.
Vision
Google Search Crawler is a Python library that makes web scraping feel intuitive. It transforms the complexity of HTTP requests, cookie management, pagination, and HTML parsing into a simple, beautiful generator pattern that any developer can understand in seconds.
Core Principles
1. Simplicity Through Elegance
The entire API surfaces through a single function: search(). Everything else is either a convenience wrapper or an internal implementation detail. Users shouldn't need to understand cookies, user agents, or URL encoding to get results.
for result in search('python programming', stop=10):
print(result['title'], result['url'])
That's it. That's the entire interface. Beautiful.
2. Generator-First Architecture
We use Python generators not for performance (though that's a bonus), but because they match the mental model perfectly. Search results are inherently sequential and potentially infinite. A generator captures this truth elegantly.
3. Fail Gracefully, Always
The web is unpredictable. Google changes their HTML. Networks fail. Rate limits trigger. Our code handles every failure gracefully, logs it properly, and recovers when possible. Users should never see a cryptic stack trace.
4. Respect The Web
We implement rate limiting not because we have to, but because it's the right thing to do. We randomize user agents to avoid detection, but we also pause between requests to be respectful. Good tools should make it easy to do the right thing.
Architecture
The Three Layers
┌─────────────────────────────────────┐
│ API Layer (search, search_images) │
│ - User-facing functions │
│ - Parameter validation │
│ - Convenience wrappers │
└─────────────────────────────────────┘
↓
┌─────────────────────────────────────┐
│ Core Engine (search generator) │
│ - Pagination logic │
│ - Result parsing │
│ - Deduplication │
└─────────────────────────────────────┘
↓
┌─────────────────────────────────────┐
│ Foundation (get_page, filter) │
│ - HTTP requests │
│ - Cookie management │
│ - HTML parsing │
└─────────────────────────────────────┘
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.
- 5d ago First seen · 241 lines · 1,792 tokens per session scan A 6168b7a201e5
google-search-crawler CLAUDE.md is an instructions file published in the GitHub repository duyet/google-search-crawler (21 stars, last pushed 3mo ago), licensed MIT. It adds 1,792 tokens to every session, about $0.0090 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).