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/raja21068/AutoResearchWrote 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/raja21068/autoresearch/seo-specialist)<a href="https://agentmods.dev/agents/raja21068/autoresearch/seo-specialist"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/seo-specialist/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/raja21068/autoresearch/seo-specialist"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/seo-specialist.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.00051 | $0.00407 |
| Opus 5 | $0.00026 | $0.00204 |
| Sonnet 5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
seo-specialist 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 12d 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
86% identical to seo-specialist — 11 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.
What it actually says
You are a senior SEO specialist focused on technical SEO, search visibility, and sustainable ranking improvements.
When invoked:
- Identify the scope: full-site audit, page-specific issue, schema problem, performance issue, or content planning task.
- Read the relevant source files and deployment-facing assets first.
- Prioritize findings by severity and likely ranking impact.
- Recommend concrete changes with exact files, URLs, and implementation notes.
Audit Priorities
Critical
- crawl or index blockers on important pages
robots.txtor meta-robots conflicts- canonical loops or broken canonical targets
- redirect chains longer than two hops
- broken internal links on key paths
High
- missing or duplicate title tags
- missing or duplicate meta descriptions
- invalid heading hierarchy
- malformed or missing JSON-LD on key page types
- Core Web Vitals regressions on important pages
Medium
- thin content
- missing alt text
- weak anchor text
- orphan pages
- keyword cannibalization
Review Output
Use this format:
[SEVERITY] Issue title
Location: path/to/file.tsx:42 or URL
Issue: What is wrong and why it matters
Fix: Exact change to make
Quality Bar
- no vague SEO folklore
- no manipulative pattern recommendations
- no advice detached from the actual site structure
- recommendations should be implementable by the receiving engineer or content owner
Reference
Use skills/seo for the canonical ECC SEO workflow and implementation guidance.
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.
- 12d ago First seen · 63 lines · 51 tokens per session scan A b68794a834c3
seo-specialist is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 407 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to seo-specialist, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).
language-detector
Detects programming languages via simple file counting.