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/damimartinez/scrapeagent/claude-mdgit clone --depth 1 https://github.com/DamiMartinez/scrapeagentWrote 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/damimartinez/scrapeagent/claude-md)<a href="https://agentmods.dev/instructions/damimartinez/scrapeagent/claude-md"><img src="https://agentmods.dev/badge/instructions/damimartinez/scrapeagent/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.00816 | $0.00816 |
| Opus 5 | $0.00408 | $0.00408 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
scrapeagent 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 3d 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 — 76 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.
Commands
# Install dependencies
poetry install
# Pre-install the Playwright MCP browser tool (avoids timeout on first run)
npm install -g @playwright/mcp
# Run the agent (web UI at http://localhost:8000)
poetry run adk web
# Run all tests
poetry run pytest tests/ -v
# Run a single test file
poetry run pytest tests/test_skills_loader.py -v
# Run a single test by name
poetry run pytest tests/test_skills_loader.py::test_load_valid_skill -v
Architecture
Single root agent (LlmAgent) defined in scrapeagent/agent.py. No sub-agents. The agent's expertise lives in skill files, not the system prompt.
Skills — Progressive Disclosure (3 levels)
Skills live in scrapeagent/skills/<skill-name>/SKILL.md. The ADK SkillToolset loads them with progressive disclosure:
- L1 (startup):
name+descriptionfrom YAML frontmatter (~100 tokens/skill) - L2 (on demand): Full
SKILL.mdbody when the agent activates the skill - L3 (on demand): Files in
references/andassets/subdirectories
skills_loader.py contains the custom load_skill_from_dir() because google.adk does not expose a built-in loader. It parses YAML frontmatter + markdown body and builds google.adk.skills.models.Skill objects manually.
MCP Toolsets
mcp-server-fetch(viauvx): Lightweight HTTP for static HTML sites@playwright/mcp(vianpx --headless): Full browser for JS-heavy sites
Both use McpToolset + StdioConnectionParams(timeout=30.0). The 30s timeout is required — the default 5s is too short for npx.
Custom Tools
save_output(tools/file_tools.py): Writes scraped data to./output/as CSV, JSON, or Markdowncreate_skill(tools/file_tools.py): Creates a new skill directory +SKILL.mdat runtime; requires agent restart to load
Model
Configured via LITELLM_MODEL env var (default: gemini/gemini-2.5-flash). LiteLLM handles all provider routing. See README.md for the full model table.
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.
- 3d ago First seen · 76 lines · 816 tokens per session scan A 74227d173163
scrapeagent CLAUDE.md is an instructions file published in the GitHub repository DamiMartinez/scrapeagent (10 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 816 tokens to every session, about $0.0041 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.