What is site-seo-pipeline AGENTS.md?

Repository instructions for site-seo-pipeline, a Node.js library and command-line tool that discovers website URLs, crawls pages, researches keywords, and suggests SEO text. SEO means improving how pages appear in search engines.

Use them when developing, testing, building, or publishing this package, including work on sitemap crawling, keyword research, or generated page metadata.

They give coding agents the package layout, required commands, and publishing conventions so changes fit the existing project. They also identify source files versus generated build output.

How KaranTankshali/site-seo-pipeline configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to KaranTankshali/site-seo-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/KaranTankshali/site-seo-pipeline/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/KaranTankshali/site-seo-pipeline

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/karantankshali/site-seo-pipeline/agents-md/github.svg)](https://agentmods.dev/instructions/karantankshali/site-seo-pipeline/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/karantankshali/site-seo-pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/karantankshali/site-seo-pipeline/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/karantankshali/site-seo-pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/karantankshali/site-seo-pipeline/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,101 This file is loaded in full into every session.

When invoked 1,101 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01101	$0.01101
Opus 5	$0.00550	$0.00550
Sonnet 5	$0.00220	$0.00220
Haiku 4.5	$0.00110	$0.00110

Measured 11d ago against content hash 163a94fe938d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

site-seo-pipeline AGENTS.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 11d 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.

AGENTS.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — site-seo-pipeline

Instructions for AI coding agents and humans maintaining this package. End users should start with README.md.

What this package is

A Node.js library + CLI that:

Discovers URLs from sitemap XML (index + nested urlsets, same-origin filter).
Crawls each URL via fetch + Cheerio (default) or optional Playwright (JS-rendered sites).
Researches keywords with Google Suggest (no key) and optional SerpAPI (Google SERP JSON).
Suggests SEO copy with Google Gemini (metaTitle, metaDescription, belowTheFoldMarkdown, optional FAQs).

Published entry: dist/ (build output). Source of truth: src/.

Commands

Command	Purpose
`npm install`	Install dependencies
`npm run build`	`tsc` → `dist/` (required before publish; `prepublishOnly` runs this)
`npm test`	Vitest unit tests (mocked network / APIs)
`npm run test:coverage`	Coverage report
`npm run test:watch`	Watch mode
`node dist/cli.js --sitemap …`	Run CLI locally after build

Repository layout

src/
  index.ts          # Public exports only — add new exports here
  types.ts          # Shared TypeScript interfaces
  cli.ts            # CLI entry; parseCliConfig() is tested; main() gated by isCliMain
  sitemap/          # discover.ts, url-utils.ts — XML fetch + URL collection
  crawl/            # fetch-page.ts, extract-from-html.ts, playwright-page.ts
  research/         # google-suggest.ts, serpapi.ts, build-queries.ts, page-research.ts
  suggest/          # gemini.ts, parse-model-json.ts
  pipeline/         # run.ts (orchestration), pool.ts (concurrency)
test/               # Vitest specs; mock fetch, SerpAPI, Gemini, Playwright
vitest.config.ts
tsconfig.json

Conventions (do not break)

ESM only: "type": "module", Node 18+.
TypeScript imports use .js extensions in import paths (NodeNext resolution), e.g. from "./foo.js".
Playwright is an optional peer — do not add a top-level import "playwright" in run.ts; use dynamic import() inside the renderJs branch so the package works without Playwright installed.
External I/O: fetch for HTTP; no hardcoded secrets — keys via env or options (geminiApiKey, serpApiKey).
CLI: Importing cli.ts from tests must not auto-run main() — entry is guarded by isCliMain (import.meta.url vs process.argv[1]).

Read the full file on GitHub · 85 lines

Changes

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.

11d ago First seen · 85 lines · 1,101 tokens per session scan A 163a94fe938d

Subscribe to this mod's changes

site-seo-pipeline AGENTS.md is an instructions file published in the GitHub repository KaranTankshali/site-seo-pipeline (4 stars, last pushed 5mo ago), licensed MIT. It adds 1,101 tokens to every session, about $0.0055 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.

Marketing and SEO

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

site-seo-pipeline: Instructions file for Codex