pseo-linking

pseo-linking is a skill for Claude Code from lisbeth718/pseo-skills. It costs 55 tokens per session (1,790 once invoked), scanned A, original, MIT.

A system for connecting related pages within a website using category hubs, child pages, breadcrumbs, and related-page links. It is designed for programmatic SEO, where many pages are generated from structured data and need a clear path for visitors and search engines.

In plain words
What is it for?
Use it to build internal links, breadcrumb navigation, category hubs, related-page sections, topical clusters, and links that keep pages within a few clicks of the homepage.
Why use it?
It helps prevent pages from becoming isolated and makes the site's topic structure easier to navigate and crawl. It also gives links descriptive labels and organizes pages into related groups.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Install

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.

agentmods
npx agentmods add skills/lisbeth718/pseo-skills/pseo-linking
Any agent
npx skills add lisbeth718/pseo-skills --skill pseo-linking
Clone the repo
git clone --depth 1 https://github.com/lisbeth718/pseo-skills

Made for: Claude Code.

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 pseo-linking

README.md
[![agentmods](https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-linking.svg)](https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-linking)
Your own site
<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-linking"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-linking.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,790 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00055 $0.01790
Opus 5 $0.00028 $0.00895
Sonnet 5 $0.00011 $0.00358
Haiku 4.5 $0.00006 $0.00179

Measured 6d ago against content hash 17dcf3468baa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

pseo-linking 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.

skills/pseo-linking/SKILL.md · 212 lines

How it starts

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

pSEO Internal Linking

Build an internal linking system that creates strong topical authority, distributes link equity, and ensures every page is discoverable.

Core Principles

  1. Hub-and-spoke architecture: Category hubs link to all child pages; child pages link back to their hub
  2. Topical clustering: Pages within the same topic cluster interlink
  3. Every page reachable: No orphan pages — every page is linked from at least 2 other pages
  4. Crawl depth <= 3: Any page reachable within 3 clicks from the homepage
  5. Descriptive anchor text: Link text describes the target page, not generic "click here"

Architecture

Homepage
├── Category Hub A ──→ Page A1, A2, A3, ...
│   ├── Page A1 ──→ Hub A, A2, A3 (related)
│   ├── Page A2 ──→ Hub A, A1, A3 (related)
│   └── Page A3 ──→ Hub A, A1, A2 (related)
├── Category Hub B ──→ Page B1, B2, B3, ...
│   └── ...
└── Sitemap (links all hubs)

Implementation Steps

1. Breadcrumb Navigation

Build a breadcrumb component that:

  • Renders the full path: Home > Category > Current Page
  • Uses semantic HTML (<nav> with <ol>)
  • Generates BreadcrumbList schema markup (coordinate with pseo-schema)
  • Appears on every pSEO page
interface BreadcrumbItem {
  label: string;
  href: string;
}

function Breadcrumbs({ items }: { items: BreadcrumbItem[] }) {
  return (
    <nav aria-label="Breadcrumb">
      <ol>
        {items.map((item, i) => (
          <li key={item.href}>
            {i < items.length - 1 ? (
              <a href={item.href}>{item.label}</a>
            ) : (
              <span aria-current="page">{item.label}</span>
            )}
          </li>
        ))}
      </ol>
    </nav>
  );
}

2. Related Pages Component

Build a component that displays links to related pages:

  • Pull related pages from the data layer's getRelatedPages(slug, limit) function
  • Show 3-6 related pages per page
  • Prioritize pages in the same category, then adjacent categories
  • Use the page's H1 or title as anchor text
  • Include a brief description or differentiator for each link

Read the full file on GitHub · 212 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.

  1. 6d ago First seen · 212 lines · 55 tokens per session scan A 17dcf3468baa

Subscribe to this mod's changes

pseo-linking is a skill published in the GitHub repository lisbeth718/pseo-skills (53 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 1,790 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 95 tokens