Borrowing it
Nothing to install: this file belongs to umutxyp/Seo-Promt-Master. 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/umutxyp/Seo-Promt-Master/main/GEMINI.mdgit clone --depth 1 https://github.com/umutxyp/Seo-Promt-MasterWrote 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/umutxyp/seo-promt-master/gemini-md)<a href="https://agentmods.dev/instructions/umutxyp/seo-promt-master/gemini-md"><img src="https://agentmods.dev/badge/instructions/umutxyp/seo-promt-master/gemini-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/umutxyp/seo-promt-master/gemini-md"><img src="https://agentmods.dev/badge/instructions/umutxyp/seo-promt-master/gemini-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.00567 | $0.00567 |
| Opus 5 | $0.00283 | $0.00283 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
Seo-Promt-Master GEMINI.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 10d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Prompt Master
This repository is a prompt-driven SEO audit-and-fix workflow with a runnable live audit tool. If it is in your context — on its own, or dropped alongside another project — you have everything needed to bring that project's public pages into compliance with Google's documented guidance.
Read START.md and execute its phases in order. Begin without asking.
The short version
- Knowledge base:
docs/01–docs/17, distilled from Google Search Central and web.dev. It is the only source of truth. Never assert a Google rule that is not in there — say "not covered by the knowledge base" instead. - Industry overlays:
verticals/01–24. Additive, never a replacement. - Phases:
prompts/00–04, plus optional05for live field data. - Progress files:
ROUTES-INVENTORY.mdandSEO-AUDIT-PROGRESS.md. Check whether they already exist and resume rather than restarting. - Output: a computed SEO Score and GEO Score out of 100 (
docs/11), with a category breakdown and the off-page caveat.
Run the tool
node tools/seo-audit.mjs --url https://the-site.example --max 40 --md seo-report.md
Zero dependencies, Node 18+. Reading the code tells you what the project
intends; this tells you what the server actually returns. Both matter, and they
disagree more often than you would expect. Exits 1 if any P1 finding is open.
Ground rules
- Fix shared infrastructure (metadata helper, sitemap, robots, i18n) before per-page work — it fixes hundreds of pages at once.
- Typecheck, lint and build after every change. Never leave the build broken.
- A page is fixed when you have re-fetched it and seen the change, not when you have edited the file.
- Do not pause between phases or pages to ask whether to continue. Stop only if you cannot access the repo or build it, or if a finding needs a real product decision — ask that one question and carry on with everything else.
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.
- 10d ago First seen · 51 lines · 567 tokens per session scan A f2de88b95567
Seo-Promt-Master GEMINI.md is an instructions file published in the GitHub repository umutxyp/Seo-Promt-Master (547 stars, last pushed 25d ago), licensed MIT. It adds 567 tokens to every session, about $0.0028 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
pluribus copilot-instructions.md
Instructions for caioribeiroclw-pixel/pluribus, covering project, stack, conventions, constraints and goals.
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.