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 skills/lisbeth718/pseo-skills/pseo-schemanpx skills add lisbeth718/pseo-skills --skill pseo-schemagit clone --depth 1 https://github.com/lisbeth718/pseo-skillsWrote 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/skills/lisbeth718/pseo-skills/pseo-schema)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-schema"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-schema.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.1 | $0.00056 | $0.01748 |
| Opus 5 | $0.00028 | $0.00874 |
| Sonnet 5 | $0.00011 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
pseo-schema 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 6d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pSEO Schema Markup
Implement JSON-LD structured data that gives search engines explicit semantic understanding of every programmatic page.
Core Principles
- JSON-LD format: Always use JSON-LD, not Microdata or RDFa
- Context-appropriate types: Match schema type to the page's actual content
- Data-driven generation: Schema is built from the same data that drives the page
- Valid and complete: Every schema block must pass Google's Rich Results Test
- No fabrication: Only include fields backed by real data
Baseline Schema (Every Page)
Every pSEO page should include these foundational types:
WebSite— once per site (on the homepage or via a shared layout), declares site-level search and nameWebPage— on every page, declares the page URL, name, description, and dateModifiedBreadcrumbList— on every page with navigation hierarchy
These are in addition to the content-specific types below.
Schema Types by Page Context
| Page Type | Primary Schema | Supporting Schema |
|---|---|---|
| Content/article page | Article |
BreadcrumbList, FAQPage, WebPage |
| Product page | Product |
BreadcrumbList, AggregateRating, WebPage |
| FAQ/Q&A page | FAQPage |
BreadcrumbList, WebPage |
| How-to/tutorial page | HowTo |
BreadcrumbList, FAQPage, WebPage |
| Category/hub page | CollectionPage |
BreadcrumbList, ItemList, WebPage |
| Local/location page | LocalBusiness |
BreadcrumbList, FAQPage, WebPage |
Implementation Steps
1. Create Schema Generator Functions
Build a module of pure functions that produce schema objects from page data:
// lib/schema.ts
export function generateArticleSchema(data: PageData, url: string) {
return {
"@context": "https://schema.org",
"@type": "Article",
headline: data.h1,
description: data.metaDescription,
url,
datePublished: data.publishedDate,
dateModified: data.lastModified,
author: { "@type": "Organization", name: "..." },
publisher: { "@type": "Organization", name: "..." },
};
}
// IMPORTANT: FAQPage schema is ONLY valid when the FAQ content is
// visible on the page itself. Google requires the questions and answers
// to be present in the rendered HTML, not just in the JSON-LD.
// Never add FAQPage schema to a page that does not render the FAQs.
export function generateFAQSchema(faqs: FAQ[]) {
if (!faqs?.length) return null;
return {
"@context": "https://schema.org",
"@type": "FAQPage",
mainEntity: faqs.map((faq) => ({
"@type": "Question",
name: faq.question,
acceptedAnswer: {
"@type": "Answer",
text: faq.answer,
},
})),
};
}
export function generateWebPageSchema(data: PageData, url: string) {
return {
"@context": "https://schema.org",
"@type": "WebPage",
name: data.title,
description: data.metaDescription,
url,
dateModified: data.lastModified,
};
}
export function generateBreadcrumbSchema(
items: { name: string; url: string }[]
) {
return {
"@context": "https://schema.org",
"@type": "BreadcrumbList",
itemListElement: items.map((item, i) => ({
"@type": "ListItem",
position: i + 1,
name: item.name,
item: item.url,
})),
};
}
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.
- 6d ago First seen · 215 lines · 56 tokens per session scan A f04291f1a92a
pseo-schema is a skill published in the GitHub repository lisbeth718/pseo-skills (53 stars, last pushed 7mo ago), licensed MIT. It adds 56 tokens to every session and 1,748 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…