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/Fmarzochi/EGCWrote 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/fmarzochi/egc/seo-specialist)<a href="https://agentmods.dev/agents/fmarzochi/egc/seo-specialist"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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/fmarzochi/egc/seo-specialist"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00418 |
| Opus 5.5 | $0.00020 | $0.00167 |
| Sonnet 5.5 | $0.00010 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
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 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
84% identical to seo-specialist — 16 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 EGC 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.
- 1mo ago First seen · 64 lines · 51 tokens per session scan A 1c2e7be29bdc
seo-specialist is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 418 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to seo-specialist, differing in 16 lines, and is treated as a copy.
Other agents, from other repositories
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.