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.
git clone --depth 1 https://github.com/seite-sh/seiteWrote 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/agents/seite-sh/seite/internal-linker)<a href="https://agentmods.dev/agents/seite-sh/seite/internal-linker"><img src="https://agentmods.dev/badge/agents/seite-sh/seite/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.
<a href="https://agentmods.dev/agents/seite-sh/seite/internal-linker"><img src="https://agentmods.dev/badge/agents/seite-sh/seite/internal-linker.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02402 |
| Opus 5.5 | $0.00000 | $0.00961 |
| Sonnet 5.5 | $0.00000 | $0.00480 |
| Haiku 4.5 | $0.00000 | $0.00240 |
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 1mo 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.
This is a copy
100% identical to internal-linker — 0 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.
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
- User Value: Help readers discover related helpful content
- SEO Value: Distribute page authority and strengthen topic clusters
- Conversion Path: Guide readers toward high-value pages (pillar, product, tools)
- Engagement: Increase time on site and reduce bounce rate
- 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
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.
- 1mo ago First seen · 276 lines · 0 tokens per session scan A 8d69c89aef7a
internal-linker is an agent published in the GitHub repository seite-sh/seite (25 stars, last pushed 4d 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. It is 100% identical to internal-linker, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
risk-manager
Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses. Use PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.