agentmods.dev

google-maps-scraper AGENTS.md

Development instructions for Google Maps Scraper, a Go program for collecting information from Google Maps. They cover commands, code style, error handling, testing, linting, and formatting.

In plain words
What is it for?
Use them when adding or changing scraper code, running package or race-enabled tests, checking code quality, and formatting the project.
Why use it?
They reduce mistakes in Go code and make sure changes are checked in the same way as the rest of the project.

Instructions file for CodexOpenCode

5.7k +32 10d ago A scan 289 tokens original MIT
View the source file gosom/google-maps-scraper
Install

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.

agentmods
npx agentmods add instructions/gosom/google-maps-scraper/agents-md
Clone the repo
git clone --depth 1 https://github.com/gosom/google-maps-scraper

Made for: Codex, OpenCode.

Per session 289 This file is loaded in full into every session.
When invoked 289 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00289 $0.00289
Opus 5 $0.00144 $0.00144
Sonnet 5 $0.00058 $0.00058
Haiku 4.5 $0.00029 $0.00029

Measured 2d ago against content hash c779c1eb7ad0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

google-maps-scraper AGENTS.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 2d 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.

AGENTS.md · 24 lines

What it actually says

Development Guide for Agents

Build/Test Commands

  • make test - Run all unit tests with race detection
  • make test-cover - Run tests with coverage statistics
  • make lint - Run golangci-lint with project configuration
  • make vet - Run go vet static analysis
  • make format - Format code with gofmt
  • go test ./path/to/package - Run tests for a specific package

Code Style Guidelines

  • Use gofmt for formatting (spaces, not tabs)
  • Import order: standard library, third-party, local packages (prefix: github.com/gosom/google-maps-scraper)
  • Use descriptive variable names (e.g., entry, cfg, ctx)
  • Error handling: return errors, use fmt.Errorf with wrapping (%w)
  • Use struct tags for JSON marshaling: json:"field_name"
  • Constants use CamelCase (e.g., RunModeFile)
  • Interface names end with -er suffix (e.g., Runner, S3Uploader)
  • Use context.Context as first parameter in functions
  • Prefer early returns to reduce nesting
  • Use meaningful package names that reflect their purpose
  • Add godoc comments for exported types and functions
  • Use nolint comments sparingly with explanations
  • Avoid magic numbers, use named constants or comment them
Changes

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.

  1. 2d ago First seen · 24 lines · 289 tokens per session scan A c779c1eb7ad0

Subscribe to this mod's changes

google-maps-scraper AGENTS.md is an instructions file published in the GitHub repository gosom/google-maps-scraper (5,697 stars, last pushed 10d ago), licensed MIT. It adds 289 tokens to every session, about $0.0014 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-30.

distributed-scraperdistributed-scrapinggoogle-maps-scrapingweb-scraperweb-scraping
Related

Other instructions, from other repositories

Scrapegraph-ai AGENTS.md

Instructions for ScrapeGraphAI/Scrapegraph-ai, covering agents.md, 1. golden rule: everything goes to pre/beta, 1. always start from an up-to-date pre/beta, 2. commit your work and 3. push and open the pr against pre/beta.

ScrapeGraphAI/Scrapegraph-ai · 1,314 tokens

ketch AGENTS.md

Instructions for 1broseidon/ketch, covering ketch — architecture, module layout, design principles, mcp server and quality standards.

1broseidon/ketch · 3,171 tokens

AutomatiQ AGENTS.md

Instructions for StoneSteel27/AutomatiQ, covering agent guidelines, background context, our partner: nodemaven, package structure and important commands.

StoneSteel27/AutomatiQ · 1,669 tokens

servo-fetch AGENTS.md

Instructions for konippi/servo-fetch, covering agents.md, project overview, setup and commands, code conventions and rust style.

konippi/servo-fetch · 1,928 tokens

ketch CLAUDE.md

Instructions for 1broseidon/ketch, covering ketch, architecture, build & test, output format and output flags (all commands).

1broseidon/ketch · 3,371 tokens

rdrr CLAUDE.md

Instructions for fkonovalov/rdrr, covering claude.md, what is this project?, project structure, common commands and code conventions.

fkonovalov/rdrr · 1,152 tokens