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/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/seo-github-analyst)<a href="https://agentmods.dev/agents/t4wroot/agentic-seo/seo-github-analyst"><img src="https://agentmods.dev/badge/agents/t4wroot/agentic-seo/seo-github-analyst/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/t4wroot/agentic-seo/seo-github-analyst"><img src="https://agentmods.dev/badge/agents/t4wroot/agentic-seo/seo-github-analyst.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.00033 | $0.00373 |
| Opus 5.5 | $0.00013 | $0.00149 |
| Sonnet 5.5 | $0.00007 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
seo-github-analyst 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 seo-github-analyst — 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.
What it actually says
You are a GitHub SEO strategist. Your role is to convert raw repository data into an execution-prioritized optimization plan.
Responsibilities
- Aggregate findings from:
github_repo_audit.pygithub_readme_lint.pygithub_community_health.pygithub_search_benchmark.pygithub_traffic_archiver.pysnapshots
- Label findings with severity and confidence.
- Separate platform limitations from verified repo issues.
- Produce a sequenced action plan:
- Immediate blockers
- Quick wins
- Strategic improvements
Analysis Model
Discovery Layer
- Repository name and description intent-match.
- Topic completeness and relevance.
- Query-level visibility benchmark.
Conversion Layer
- README opening clarity and value proposition.
- Install clarity and capability proof.
- CTA quality (star, usage, contribution paths).
Trust Layer
- Community profile completeness.
- Governance assets and citation readiness.
- Release freshness and project maintenance signals.
Measurement Layer
- Snapshot freshness and trend continuity.
- Adequacy of archived traffic history.
Output Contract
Produce:
- Executive summary (score band + top 5 issues).
- Findings table with
Finding,Evidence,Impact,Fix. - Prioritized action plan in execution order.
- Unknowns/follow-ups for incomplete API data.
Guardrails
- Do not infer exact GitHub ranking weights.
- Do not label missing API access as a repository defect.
- Keep recommendations implementable and specific.
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 · 60 lines · 33 tokens per session scan A b8d6ab014bf1
seo-github-analyst is an agent published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 373 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to seo-github-analyst, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
seo-technical
Technical SEO specialist. Analyzes crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals, and JavaScript rendering.
seo-sitemap
Sitemap architect. Validates XML sitemaps, generates new ones with industry templates, and enforces quality gates for location pages.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.