gitscape.ai: Skill for Claude Code

.agents/skills/programmatic-seo/SKILL.md

programmatic-seo is a skill for Claude Code, Codex from jmxt3/gitscape.ai. It costs 132 tokens per session (1,633 once invoked), scanned A, a copy of programmatic-seo, Apache-2.0.

A method for creating many search-optimized web pages from reusable templates and structured data. Examples include directory pages, location pages, comparison pages, and integration pages.

In plain words
What is it for?
Use it to plan template-based SEO pages, choose page variations, assess search opportunities, and build large sets of location, comparison, directory, or integration pages.
Why use it?
It provides a way to cover repeated search needs while requiring each page to offer useful, page-specific information rather than thin copied text.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is jmxt3/gitscape.ai's own configuration. It tells Claude Code and Codex how to work on gitscape.ai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gitscape.ai configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jmxt3/gitscape.ai. 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/jmxt3/gitscape.ai/main/.agents/skills/programmatic-seo/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jmxt3/gitscape.ai

Made for: Claude Code, Codex.

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.

agentmods badge for programmatic-seo

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmxt3/gitscape.ai/programmatic-seo/github.svg)](https://agentmods.dev/skills/jmxt3/gitscape.ai/programmatic-seo)
Your own site
<a href="https://agentmods.dev/skills/jmxt3/gitscape.ai/programmatic-seo"><img src="https://agentmods.dev/badge/skills/jmxt3/gitscape.ai/programmatic-seo/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.

agentmods 80×15 button for programmatic-seo

Your own site · 80×15
<a href="https://agentmods.dev/skills/jmxt3/gitscape.ai/programmatic-seo"><img src="https://agentmods.dev/badge/skills/jmxt3/gitscape.ai/programmatic-seo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,633 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00132 $0.01633
Opus 5 $0.00066 $0.00816
Sonnet 5 $0.00026 $0.00327
Haiku 4.5 $0.00013 $0.00163

Measured 9d ago against content hash 3f5b405f4058, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

programmatic-seo 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.

Origin

This is a copy

100% identical to programmatic-seo — 8 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.

.agents/skills/programmatic-seo/SKILL.md · 239 lines

How it starts

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

Programmatic SEO

You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a programmatic SEO strategy, understand:

  1. Business Context

    • What's the product/service?
    • Who is the target audience?
    • What's the conversion goal for these pages?
  2. Opportunity Assessment

    • What search patterns exist?
    • How many potential pages?
    • What's the search volume distribution?
  3. Competitive Landscape

    • Who ranks for these terms now?
    • What do their pages look like?
    • Can you realistically compete?

Core Principles

1. Unique Value Per Page

  • Every page must provide value specific to that page
  • Not just swapped variables in a template
  • Maximize unique content—the more differentiated, the better

2. Proprietary Data Wins

Hierarchy of data defensibility:

  1. Proprietary (you created it)
  2. Product-derived (from your users)
  3. User-generated (your community)
  4. Licensed (exclusive access)
  5. Public (anyone can use—weakest)

3. Clean URL Structure

Use subfolders, not subdomains — subfolders consolidate domain authority while subdomains split it:

  • Good: yoursite.com/templates/resume/
  • Bad: templates.yoursite.com/resume/

4. Genuine Search Intent Match

Pages must actually answer what people are searching for.

5. Quality Over Quantity

Better to have 100 great pages than 10,000 thin ones.

6. Avoid Google Penalties

  • No doorway pages
  • No keyword stuffing
  • No duplicate content
  • Genuine utility for users

The 12 Playbooks (Overview)

Playbook Pattern Example
Templates "[Type] template" "resume template"
Curation "best [category]" "best website builders"
Conversions "[X] to [Y]" "$10 USD to GBP"
Comparisons "[X] vs [Y]" "webflow vs wordpress"
Examples "[type] examples" "landing page examples"
Locations "[service] in [location]" "dentists in austin"
Personas "[product] for [audience]" "crm for real estate"
Integrations "[product A] [product B] integration" "slack asana integration"
Glossary "what is [term]" "what is pSEO"
Translations Content in multiple languages Localized content
Directory "[category] tools" "ai copywriting tools"
Profiles "[entity name]" "stripe ceo"

Read the full file on GitHub · 239 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 9d ago First seen · 239 lines · 132 tokens per session scan A 3f5b405f4058

Subscribe to this mod's changes

programmatic-seo is a skill published in the GitHub repository jmxt3/gitscape.ai (33 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 132 tokens to every session and 1,633 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to programmatic-seo, differing in 8 lines, and is treated as a copy.

Related

Other skills, from other repositories

ultralytics-platform

This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…

fcakyon/claude-codex-settings · 112 tokens

mindos

Operate a MindOS knowledge base: update notes, search, organize files, execute SOPs/workflows, retrospective, append CSV, cross-agent handoff, route unstructured input to the right files, distill experience, sync related docs. Use when the task targets files inside the user's MindOS KB (mindRoot). NOT for editing app…

GeminiLight/MindOS · 157 tokens

mongodb-query-optimizer

Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…

fcakyon/claude-codex-settings · 98 tokens

rag-retrieval

Retrieval-Augmented Generation patterns for grounded LLM responses. Use when building RAG pipelines, embedding documents, implementing hybrid search, contextual retrieval, HyDE, agentic RAG, multimodal RAG, query decomposition, reranking, or pgvector search.

yonatangross/orchestkit · 58 tokens

github

GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.

AIOSAI/AIPass · 23 tokens

github-image-upload

Upload local images and other files (PDF, zip, log, …) to GitHub and embed them in a pull request description, an issue, or a comment — producing canonical github.com/user-attachments URLs (private-repo uploads stay private). Use when asked to "attach a screenshot to the PR", "add an image to the PR description", "put…

drogers0/gh-image · 135 tokens