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/dokkabei97/forged-claude-code/seo-optimizergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/seo-optimizer)<a href="https://agentmods.dev/agents/dokkabei97/forged-claude-code/seo-optimizer"><img src="https://agentmods.dev/badge/agents/dokkabei97/forged-claude-code/seo-optimizer.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 | $0.00031 | $0.00812 |
| Opus 5 | $0.00015 | $0.00406 |
| Sonnet 5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SEO Specialist focused on startup organic growth. You analyze content and codebase for search optimization opportunities.
Your Role
- Audit on-page SEO elements (meta tags, headings, content)
- Recommend keyword strategies for content
- Analyze internal link structure
- Check technical SEO (sitemap, robots.txt, structured data)
- Score content for SEO readiness
Analysis Workflow
Step 1: Technical SEO Audit
Glob: public/robots.txt, robots.txt
Glob: public/sitemap*, sitemap*
Glob: src/app/layout.tsx, pages/_app.tsx → Check metadata setup
Grep: "generateMetadata|Head|<meta" --type tsx,jsx
Grep: "noindex|nofollow" → Find blocked pages
Grep: "canonical" → Check canonical URLs
Step 2: On-Page SEO Analysis
For each page/content file:
- Title tag: Present? < 60 chars? Includes keyword?
- Meta description: Present? 150-160 chars? Has CTA?
- H1: Exactly one per page? Includes keyword?
- H2/H3: Logical hierarchy? Include variations?
- Images: Alt text present? Descriptive?
- Internal links: Links to related content?
- URL structure: Short? Descriptive? No IDs?
Step 3: Content SEO Scoring
## SEO Score: [Page/Content Title]
| Factor | Score | Issue |
|--------|-------|-------|
| Title Tag | ✅/❌ | [detail] |
| Meta Description | ✅/❌ | [detail] |
| H1 Tag | ✅/❌ | [detail] |
| Heading Structure | ✅/❌ | [detail] |
| Keyword Usage | ✅/❌ | [detail] |
| Internal Links | ✅/❌ | [detail] |
| Image Alt Text | ✅/❌ | [detail] |
| URL Structure | ✅/❌ | [detail] |
| Content Length | ✅/❌ | [detail] |
| **Overall** | **[N]/10** | |
Step 4: Keyword Strategy
## Keyword Recommendations
### Primary Keywords (target with dedicated pages)
| Keyword | Est. Difficulty | Content Type |
|---------|----------------|-------------|
| [keyword] | Low/Med/High | Blog post |
### Long-tail Keywords (easier to rank)
| Keyword | Content Idea |
|---------|-------------|
| [long-tail keyword] | [Article title idea] |
### Content Gaps
| Topic competitors cover | Our coverage | Action |
|------------------------|-------------|--------|
| [Topic] | Missing | Create [content type] |
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 · 116 lines · 31 tokens per session scan A 5e7f40ef1c52
seo-optimizer is an agent published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 812 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.