Borrowing it
Nothing to install: this file belongs to adamkristopher/seo-dfs-cc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adamkristopher/seo-dfs-cc/main/CLAUDE.mdgit clone --depth 1 https://github.com/adamkristopher/seo-dfs-ccWrote 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/adamkristopher/seo-dfs-cc/claude-md)<a href="https://agentmods.dev/instructions/adamkristopher/seo-dfs-cc/claude-md"><img src="https://agentmods.dev/badge/instructions/adamkristopher/seo-dfs-cc/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.01616 | $0.01616 |
| Opus 5 | $0.00808 | $0.00808 |
| Sonnet 5 | $0.00323 | $0.00323 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
seo-dfs-cc 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 8d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DataForSEO Keyword Research Toolkit
Overview
This is a Python toolkit for keyword research using the DataForSEO API. Claude executes research functions on your behalf and saves structured results to JSON files, then creates human-readable summary documents for decision-making.
Project Structure
/Users/adamcarter/Desktop/SEO/
├── .env # API credentials (DO NOT COMMIT)
├── main.py # High-level convenience functions
├── config/
│ └── settings.py # Configuration and defaults
├── core/
│ ├── client.py # DataForSEO API client (singleton)
│ └── storage.py # Auto-save results to JSON
├── api/
│ ├── keywords_data.py # Search volume, CPC, competition
│ ├── labs.py # Suggestions, difficulty, intent
│ ├── serp.py # Google/YouTube rankings
│ └── trends.py # Google Trends data
└── results/
├── keywords_data/ # Raw JSON from Keywords Data API
├── labs/ # Raw JSON from Labs API
├── serp/ # Raw JSON from SERP API
├── trends/ # Raw JSON from Trends API
└── summary/ # Human-readable markdown summaries
How to Use (Prompting Claude)
Basic Research Requests
Just tell Claude what you want to research:
- "Research keywords for [topic]"
- "Get YouTube keyword data for [video idea]"
- "Find keyword suggestions for [seed keyword]"
- "Analyze competitor [domain.com]"
- "What's trending in [category]"
Specific Function Requests
For more control, request specific functions:
- "Run
get_keyword_suggestionsfor 'AI website builders'" - "Get
get_youtube_serpfor these keywords: [list]" - "Use
get_bulk_keyword_difficultyon [keywords]"
Summary Requests
After running research, ask for summaries:
- "Create a summary of those results in /results/summary"
- "Put the results in a document named [specific-name].md"
- "Summarize the data so I can make decisions"
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.
- 8d ago First seen · 200 lines · 1,616 tokens per session scan A 67094fe9d022
seo-dfs-cc CLAUDE.md is an instructions file published in the GitHub repository adamkristopher/seo-dfs-cc (11 stars, last pushed 9mo ago), licensed MIT. It adds 1,616 tokens to every session, about $0.0081 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.
Other instructions, from other repositories
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.
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).
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).
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.
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.