Borrowing it
Nothing to install: this file belongs to prashishh/seo-geo-report-engine. 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/prashishh/seo-geo-report-engine/main/CLAUDE.mdgit clone --depth 1 https://github.com/prashishh/seo-geo-report-engineWrote 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/prashishh/seo-geo-report-engine/claude-md)<a href="https://agentmods.dev/instructions/prashishh/seo-geo-report-engine/claude-md"><img src="https://agentmods.dev/badge/instructions/prashishh/seo-geo-report-engine/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/prashishh/seo-geo-report-engine/claude-md"><img src="https://agentmods.dev/badge/instructions/prashishh/seo-geo-report-engine/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.02160 | $0.02160 |
| Opus 5 | $0.01080 | $0.01080 |
| Sonnet 5 | $0.00432 | $0.00432 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
seo-geo-report-engine 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 9d 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.
This is a copy
100% identical to seo-geo-report-engine AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-geo-report-engine — operating manual
This is the parent framework for running marketing / SEO / GEO / growth engagements.
Capabilities (skills, workflows, tools, templates, playbooks) live here, in the parent.
Each client lives in projects/<client>/ and is pure data — it inherits every capability
from this parent. Build a capability once; every project gets it.
Works two ways: (1) launch Claude Code in this folder and everything is in scope, or (2) install this folder as a plugin (
seo-geo-report-engine) and the skills/commands/agents are available anywhere. Same source of truth (.claude/symlinks → rootskills|commands|agents).
Operating model — the brain, not the builder
This framework produces strategy and handoff-ready artifacts; it does not publish, deploy, or ship anything to a live site. That is always the client's own team's job. What it delivers:
- Strategy — positioning, keyword/page architecture, GTM, prioritization.
- Findings — trends, live data reads, competitor movement, what changed and why.
- Ready-to-implement artifacts — briefs, page specs/HTML, schema, llms.txt — handed off for the client's engineers/CMS team to build and ship on their own timeline and review process.
- Feedback — recommendations, risk flags, and a falsifiable read on what's working.
So: no skill or workflow should assume it needs "CMS access" or "publish access" to finish its job — the job is done when the deliverable is handoff-ready. Dashboard/status language says "ready to hand off" and "needs review before handoff," never "ready to publish." When a project's BUILD-STATUS lists open items, frame them as what the client's team needs to confirm or supply.
Client-facing copy rules. Reports name competitors and cite real numbers (no vague euphemisms), never name the underlying data providers (use neutral source labels: "live search data", "public review data", "public company profiles"), label every modeled figure an estimate, and drop uncertain data rather than show it. No em dashes in client copy.
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.
- 9d ago First seen · 158 lines · 2,160 tokens per session scan A f3a32e335b09
seo-geo-report-engine CLAUDE.md is an instructions file published in the GitHub repository prashishh/seo-geo-report-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 2,160 tokens to every session, about $0.0108 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-geo-report-engine AGENTS.md, differing in 0 lines, and is treated as a copy.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.