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/jadedagher/seo-agent-stack/claude-mdgit clone --depth 1 https://github.com/jadedagher/seo-agent-stackWrote 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/jadedagher/seo-agent-stack/claude-md)<a href="https://agentmods.dev/instructions/jadedagher/seo-agent-stack/claude-md"><img src="https://agentmods.dev/badge/instructions/jadedagher/seo-agent-stack/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.03327 | $0.03327 |
| Opus 5 | $0.01664 | $0.01664 |
| Sonnet 5 | $0.00665 | $0.00665 |
| Haiku 4.5 | $0.00333 | $0.00333 |
Grade A, and why
seo-agent-stack 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 3d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{PROJECT_NAME}} — SEO Project
Configuration (FILL IN)
Instructions: Replace all
{{...}}values with your own information. Once filled, this file is the single source of truth for all agents. The/setupcommand can fill this automatically.
| Variable | Value |
|---|---|
| Site URL | {{SITE_URL}} |
| Site Name | {{SITE_NAME}} |
| Sector | {{SECTOR}} (e.g., medical imaging, e-commerce, SaaS, restaurant) |
| Content Language | {{LANGUAGE}} (e.g., fr, en, es) |
| CSS Prefix | ss- (default — SEO Stack) |
Credentials & Connections (FILL IN)
| Resource | Identifier |
|---|---|
| Webflow Site ID | {{WEBFLOW_SITE_ID}} |
| Webflow Workspace ID | {{WEBFLOW_WORKSPACE_ID}} |
| GA4 Property ID | {{GA4_PROPERTY_ID}} |
| GSC Property | {{GSC_PROPERTY}} (e.g., sc-domain:example.com) |
Webflow CMS Collections (FILL IN)
List your Webflow collections. The
/setupcommand auto-discovers these. Agents use these IDs to publish content.
| Collection | ID | Slug | Items |
|---|---|---|---|
| Articles (blog) | {{COLLECTION_ARTICLES_ID}} |
/{{ARTICLES_SLUG}} |
— |
| Service Pages | {{COLLECTION_SERVICES_ID}} |
/{{SERVICES_SLUG}} |
— |
| Sub-pages | {{COLLECTION_SUBPAGES_ID}} |
/{{SUBPAGES_SLUG}} |
— |
Note: You may have fewer or more collections. Add/remove rows as needed.
CMS Schema — Articles (main blog collection)
Adapt this schema to your actual Webflow fields. The
/setupcommand auto-detects these.
| Field | Type | Required | Notes |
|---|---|---|---|
name |
PlainText | yes | Article title |
slug |
PlainText | yes | URL slug (max 256 chars, alphanum) |
meta-description |
PlainText | yes | Max 150 characters |
short-info |
PlainText | yes | Short description |
category |
PlainText | yes | Category (free text) |
thumb-image |
Image | yes | Thumbnail — {{THUMB_DIMENSIONS}} px |
main-image |
Image | yes | Hero image — {{MAIN_IMAGE_DIMENSIONS}} px |
details |
RichText | yes | Article content (HTML) |
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.
- 3d ago First seen · 322 lines · 3,327 tokens per session scan A 19e1ba8a6357
seo-agent-stack CLAUDE.md is an instructions file published in the GitHub repository jadedagher/seo-agent-stack (21 stars, last pushed 5mo ago), licensed MIT. It adds 3,327 tokens to every session, about $0.0166 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
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.