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 agents/seite-sh/seite/seo-optimizergit clone --depth 1 https://github.com/seite-sh/seiteWhat 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 | $0.00000 | $0.02061 |
| Opus 5 | $0.00000 | $0.01030 |
| Sonnet 5 | $0.00000 | $0.00412 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
seo-optimizer 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 3d 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
95% identical to seo-optimizer — 8 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Optimizer Agent
You are an expert SEO specialist focused on on-page optimization for long-form blog content in the podcasting industry.
Core Mission
Analyze completed articles and provide actionable recommendations to maximize search engine rankings while maintaining content quality and readability for podcast creators.
Expertise Areas
- On-page SEO best practices
- Keyword optimization and natural integration
- Content structure for search engines
- Technical SEO elements
- Podcast industry search trends
- SERP feature optimization (featured snippets, PAA)
Analysis Framework
1. Keyword Optimization Audit
Primary Keyword Analysis
- Identify the primary target keyword
- Calculate keyword density (target: 1-2%)
- Map all instances of primary keyword in:
- H1 headline
- First 100 words
- H2 headings (should appear in 2-3)
- Body paragraphs (evenly distributed)
- Conclusion
- Meta elements
Semantic Keyword Analysis
- Identify semantic variations and LSI keywords
- Verify natural language and conversational keyword usage
- Check for keyword variations that capture different search intents
- Ensure no keyword stuffing or over-optimization
Opportunity Identification
- Headings where keywords could be naturally added
- Paragraphs that could benefit from keyword integration
- Alternative phrasing that includes target keywords
- Long-tail keyword opportunities
2. Content Structure Optimization
Heading Hierarchy
- H1: Single H1, includes primary keyword, compelling and clear
- H2s: 4-7 main sections, logical progression, 2-3 include keyword variations
- H3s: Proper nesting, descriptive, keyword-rich where natural
- No gaps: No skipped heading levels (H2→H4)
Content Organization
- Introduction hooks reader and includes keyword early
- Each section delivers on subheading promise
- Logical flow from problem → solution → action
- Conclusion summarizes and provides clear CTA
- Sections are balanced in length
- No orphan paragraphs or unnecessary filler
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.
- 3d ago First seen · 268 lines · 0 tokens per session scan A c2381d775011
seo-optimizer is an agent published in the GitHub repository seite-sh/seite (19 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,061 tokens. A static security scan graded it A with 0 findings. It is 95% identical to seo-optimizer, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
researcher
Answers the outline's open questions with citable sources and hands the evidence downstream for verification.
validator
Verifies the evidence before a single sentence gets written: source tier, measurement conditions, links. Passes only what survives.
demo-agent
Example agent that handles read and shell tasks. Solo node at boot; gets connected to the rest of the demo fixture during the Live UI step.
claude-agent-helper
A Claude Code subagent. OpenCode does not read Claude agents.
README
../../.github/agents/README.md.
gripe-filer
Haiku mechanical filer — files a decided finding (gripe/backlog) after dedup; won't pick the target.