technical-seo-schema-engineer

technical-seo-schema-engineer is a skill for Codex from sergekostenchuk/seo-llm-skill-cluster. It costs 101 tokens per session (903 once invoked), scanned A, original, MIT.

A skill for defining technical search-visibility rules for public website pages, including metadata and Schema.org structured data.

In plain words
What is it for?
Use it to plan titles, descriptions, canonical and language links, JSON-LD, social cards, sitemaps, RSS, robots.txt, and llms.txt rules by page type.
Why use it?
It gives pages consistent instructions for search engines and social previews, and helps describe visible content accurately. Schema.org is a shared format for marking up information such as articles, people, and organizations.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 <codex-skills-dir>/senior-skill-architect/scripts/lint_production_skill.py ./skills/technical-seo-schema-engineer.

Good fit Use it to plan titles, descriptions, canonical and language links, JSON-LD, social cards, sitemaps, RSS, robots.txt, and llms.txt rules by page type.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/sergekostenchuk/seo-llm-skill-cluster
agentmods
npx agentmods add skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer

Made for: 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 technical-seo-schema-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer/github.svg)](https://agentmods.dev/skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer)
Your own site
<a href="https://agentmods.dev/skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer/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 technical-seo-schema-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/technical-seo-schema-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 903 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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00101 $0.00903
Opus 5 $0.00051 $0.00451
Sonnet 5 $0.00020 $0.00181
Haiku 4.5 $0.00010 $0.00090

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

Security

Grade A, and why

technical-seo-schema-engineer 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/technical-seo-schema-engineer/SKILL.md · 91 lines

How it starts

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

Technical SEO Schema Engineer

Use this skill after information-architecture-seo has defined page roles and before live regression validation.

Read references/schema-patterns.md before designing full metadata or JSON-LD templates.

Owns

  • title and meta description rules;
  • canonical and hreflang tag templates;
  • JSON-LD schema patterns;
  • OpenGraph and Twitter card metadata;
  • sitemap, news-sitemap, RSS, robots.txt, and llms.txt output policy;
  • publisher logo and ImageObject fallback policy;
  • page-type metadata checklist.

Does Not Own

  • semantic core;
  • final URL architecture;
  • internal link graph;
  • live audit execution;
  • hidden content;
  • visual page layout.

Workflow

  1. Read url-map.yaml, page roles, content model, language groups, and visible content requirements.
  2. Select metadata and schema by page role.
  3. Define title/meta fallbacks and length guidance.
  4. Define canonical and hreflang tags from URL map.
  5. Define JSON-LD nodes that match visible page content.
  6. Define OG/Twitter image policy: media, video poster, publisher card, or fallback OG card.
  7. Define sitemap/RSS/robots/llms.txt inclusion rules.
  8. Produce schema/head guidance using assets/jsonld-templates.md and assets/head-metadata.template.html.
  9. Hand off validation to seo-regression-validator.

Non-Negotiables

  • Schema must match visible content.
  • Do not add FAQPage unless the FAQ block is visible to users.
  • Do not add review, rating, price, author, publisher, date, image, or source claims that are absent or unsupported.
  • Do not use JSON-LD to hide extra keywords, extra entities, or alternate facts.
  • NewsArticle.image must resolve to media, poster, or a stable fallback ImageObject.
  • Canonical and hreflang must follow URL architecture.
  • Current Google/schema.org/crawler rules require primary-source verification before production changes.

Safety And Privacy Boundaries

Read the full file on GitHub · 91 lines

Files

What ships with it

6 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. 11d ago First seen · 91 lines · 101 tokens per session scan A 3fb8cb8e7f22

Subscribe to this mod's changes

technical-seo-schema-engineer is a skill published in the GitHub repository sergekostenchuk/seo-llm-skill-cluster (39 stars, last pushed 3mo ago), licensed MIT. It adds 101 tokens to every session and 903 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

technocore-chat

Coordinate with other AI agents over plain HTTP GETs — shared rooms, durable notes, long-polling. No POST, no sockets, no client libraries, no account; a fetch tool is enough, and an MCP server fronts the same surface. Use when you need to leave a message for another agent, wait for one, or persist state across your…

flop-labs/technocore-chat · 79 tokens

dialectical-paper-writing

Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments…

lijinyang439-arch/dialectical-paper-writing · 93 tokens

wiki-ingest

Compile a raw source (document, URL content, meeting notes, research output) into a wikikit agent wiki — merge-don't-overwrite, log contradictions, maintain cross-references, then lint. Use whenever the user says "add this to the wiki", "ingest this", or drops new source material for a wiki maintained with…

AvalancheAI-labs/agent-wiki-kit · 77 tokens

agent-pitbook

Search and contribute to Agent Pitbook, a structured debugging pit knowledge base for coding agents. Use when Codex is diagnosing recurring local-development failures, sandbox issues, dependency installation errors, Docker or port problems, MCP/tool quirks, browser automation failures, or when a verified debugging…

laozhangzzz/agent-pitbook · 70 tokens

duckduckgo-search

Free keyless web, news, and image search via ddgs.

NousResearch/hermes-agent · 19 tokens

mcporter

List, auth, and call MCP servers/tools from the terminal.

NousResearch/hermes-agent · 16 tokens