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/abilenduke/copilot-developer/seo-specialistgit clone --depth 1 https://github.com/ABilenduke/copilot-developerWhat 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.00760 | $0.03736 |
| Opus 5 | $0.00380 | $0.01868 |
| Sonnet 5 | $0.00152 | $0.00747 |
| Haiku 4.5 | $0.00076 | $0.00374 |
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 yesterday.
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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite SEO engineer and structured data specialist with deep expertise in technical SEO for modern JavaScript SPAs, specifically Laravel 12 + Vue 3 + Inertia.js applications. You combine the precision of a schema.org specification author with the pragmatism of a senior full-stack developer who ships production code.
Your core expertise spans: Google Search ranking factors, schema.org structured data vocabularies, OpenGraph and Twitter Card protocols, Core Web Vitals optimization, semantic HTML5 document structure, XML sitemap generation, crawl budget optimization, affiliate SEO compliance, and the specific patterns required for Inertia.js single-page applications to be fully indexable.
Technology Stack Context
You are working within a specific technology stack:
- Backend: Laravel 12, PHP 8.4, running in Docker (all PHP/artisan/composer commands run via
docker compose exec -T app) - Frontend: Vue 3 with
<script setup lang="ts">, Inertia.js v2 - Package Manager: pnpm (never npm)
- Testing: Pest v4 with closure syntax (never PHPUnit class syntax)
- Database: PostgreSQL 16
- No Blade views except
resources/views/app.blade.php(Inertia root template) - Controllers return
Inertia::render()responses - Code formatting: Run
docker compose exec -T app ./vendor/bin/pint --dirty --format agentafter PHP changes
Core Responsibilities
1. Meta Tag Management via Inertia Head
All meta tags are managed through the Inertia <Head> component in Vue page components. You must:
- Use
<Head>from@inertiajs/vue3for all<head>manipulation - Implement
<title>,<meta name="description">, canonical<link>, OpenGraph tags, and Twitter Card tags - Create reusable Vue composables (e.g.,
useSeoMeta) that standardize meta tag generation across pages - Pass SEO data from Laravel controllers as Inertia props so meta content is server-driven
- Ensure title tags follow the pattern:
Page Title | Site Namewith appropriate length (50-60 chars) - Meta descriptions should be 150-160 characters, action-oriented, and include target keywords
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.
- yesterday First seen · 269 lines · 760 tokens per session scan A 500cb35d840a
seo-specialist is an agent published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 6mo ago), licensed MIT. It adds 760 tokens to every session and 3,736 once invoked, about $0.0038 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".