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/morvanzhou/data-driven-product/claude-mdgit clone --depth 1 https://github.com/MorvanZhou/data-driven-productWrote 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/morvanzhou/data-driven-product/claude-md)<a href="https://agentmods.dev/instructions/morvanzhou/data-driven-product/claude-md"><img src="https://agentmods.dev/badge/instructions/morvanzhou/data-driven-product/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.00656 | $0.00656 |
| Opus 5 | $0.00328 | $0.00328 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
data-driven-product 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 — 59 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.
Overview
This is a Claude Code skill that performs goal-driven website analysis using Google Search Console (GSC), GA4, and Bing Webmaster APIs. It collects data, audits sites for SEO/GEO readiness, and generates prioritized improvement reports with charts.
Core principle: Goal → Data → Gap → Action — every analysis starts from the website's intended user journey and finds where reality diverges.
Project Structure
skills/data-driven-product/SKILL.md— The main skill definition (workflow phases, instructions)skills/data-driven-product/scripts/— Python data collection scripts (GA4, GSC, Bing, PSI, SEO/GEO audit)skills/data-driven-product/references/— Reference docs (metrics glossary, report template, visualization guide, checklist).skills-data/data-driven-product/— Runtime data directory (created per-project when skill runs)
Python Environment
Uses uv with Python 3.12. Dependencies in skills/data-driven-product/scripts/pyproject.toml.
# Setup (once per project)
DATA_DIR=".skills-data/data-driven-product"
uv venv "$DATA_DIR/venv" --python 3.12
uv pip install -p "$DATA_DIR/venv" -r skills/data-driven-product/scripts/pyproject.toml
# Running scripts (always activate venv first)
source "$DATA_DIR/venv/bin/activate"
python skills/data-driven-product/scripts/ga4_query.py
Key Design Decisions
- All data analysis must be done through code execution — never manually read JSON and summarize. Write scripts in
$DATA_DIR/scripts/that read from$DATA_DIR/data/and output to$DATA_DIR/analysis/. - Every analysis phase must generate charts — saved as PNG to
$DATA_DIR/charts/and embedded in Markdown reports. - Credential auto-discovery —
utils.pywalks up directories to find.skills-data/, loads.env, and auto-discovers Service Account JSON fromconfigs/. - Data directory separation —
data/(raw API responses),analysis/(processed reports),charts/(visualizations),scripts/(analysis code).
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 · 59 lines · 656 tokens per session scan A 2fbd35927619
data-driven-product CLAUDE.md is an instructions file published in the GitHub repository MorvanZhou/data-driven-product (10 stars, last pushed 3mo ago), licensed MIT. It adds 656 tokens to every session, about $0.0033 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.