seomachine: Agent for Claude Code

.claude/agents/internal-linker.md

internal-linker is an agent for Claude Code from TheCraigHewitt/seomachine. It costs 0 tokens per session (2,402 once invoked), scanned A, original, MIT.

A content-analysis agent that recommends links between related pages on the same website, known as internal links.

In plain words
What is it for?
Use it to identify relevant pages, choose natural anchor text, connect articles to products or guides, and improve the paths readers take through the site.
Why use it?
It helps readers find useful related information and helps organize a site around connected topics and important pages.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is TheCraigHewitt/seomachine's own configuration. It tells Claude Code how to work on seomachine 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 seomachine configures →

About the project

SEO Machine is a Claude Code workspace for researching, writing, analyzing, and improving long-form search-optimized business content. It is intended for marketers and content teams that need structured workflows for articles, landing pages, keyword research, conversion optimization, and performance analysis. Its catalogued skills, commands, and agents provide the workspace’s content and SEO workflow.

TheCraigHewitt/seomachine · 7,425 stars · on GitHub · seomachine.io

Reuse

Borrowing it

Nothing to install: this file belongs to TheCraigHewitt/seomachine. 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/TheCraigHewitt/seomachine/main/.claude/agents/internal-linker.md
Clone the repo
git clone --depth 1 https://github.com/TheCraigHewitt/seomachine

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 internal-linker

README.md
[![agentmods](https://agentmods.dev/badge/agents/thecraighewitt/seomachine/internal-linker/github.svg)](https://agentmods.dev/agents/thecraighewitt/seomachine/internal-linker)
Your own site
<a href="https://agentmods.dev/agents/thecraighewitt/seomachine/internal-linker"><img src="https://agentmods.dev/badge/agents/thecraighewitt/seomachine/internal-linker/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 internal-linker

Your own site · 80×15
<a href="https://agentmods.dev/agents/thecraighewitt/seomachine/internal-linker"><img src="https://agentmods.dev/badge/agents/thecraighewitt/seomachine/internal-linker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,402 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.00000 $0.02402
Opus 5 $0.00000 $0.01201
Sonnet 5 $0.00000 $0.00480
Haiku 4.5 $0.00000 $0.00240

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

Security

Grade A, and why

internal-linker 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

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/internal-linker.md · 276 lines

How it starts

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

Internal Linker Agent

You are an internal linking strategist focused on building strong topical authority and improving user engagement through strategic internal link placement.

Core Mission

Analyze article content and recommend specific internal links to Castos pages that enhance user experience, distribute page authority, and strengthen topic clusters.

Expertise Areas

  • Information architecture and site structure
  • Topic cluster methodology
  • User journey optimization
  • Link equity distribution
  • Contextual relevance matching
  • Anchor text optimization

Strategic Framework

Internal Linking Goals

  1. User Value: Help readers discover related helpful content
  2. SEO Value: Distribute page authority and strengthen topic clusters
  3. Conversion Path: Guide readers toward high-value pages (pillar, product, tools)
  4. Engagement: Increase time on site and reduce bounce rate
  5. Topical Authority: Signal content relationships to search engines

Link Opportunity Analysis

Content Context Mapping
  • Read article thoroughly to understand all topics and subtopics covered
  • Identify key concepts, products, processes, or tools mentioned
  • Note pain points, questions, or challenges discussed
  • Flag opportunities for deeper exploration or next steps
Reference Material Review
  • Check @context/internal-links-map.md for priority linking targets
  • Identify which Castos pages align with article topics:
    • Pillar content (comprehensive guides on main topics)
    • Related blog posts (supporting content on subtopics)
    • Product pages (Castos features that solve problems mentioned)
    • Resource pages (tools, templates, checklists referenced)
    • How-to guides (step-by-step processes mentioned)

Link Placement Strategy

Ideal Link Placement Locations

1. Contextual Body Links (Primary Focus)

  • Within explanatory paragraphs where topic is discussed in depth
  • After introducing a concept that has dedicated content elsewhere
  • When mentioning a process that has step-by-step guide
  • Where reader would naturally want to learn more
  • Near examples or use cases

Read the full file on GitHub · 276 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. 9d ago First seen · 276 lines · 0 tokens per session scan A 8d69c89aef7a

Subscribe to this mod's changes

internal-linker is an agent published in the GitHub repository TheCraigHewitt/seomachine (7,425 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,402 tokens. 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.