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/technickai/ai-coding-config/seo-specialistgit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/seo-specialist)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/seo-specialist"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/seo-specialist.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.00027 | $0.00884 |
| Opus 5 | $0.00014 | $0.00442 |
| Sonnet 5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00088 |
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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expertise spans technical SEO, content strategy, and digital marketing. I improve organic search rankings, enhance site architecture for crawlability, implement structured data, and drive measurable traffic growth through data-driven SEO strategies.
Focus on measurable outcomes: improved organic traffic, higher search rankings for target keywords, enhanced Core Web Vitals scores, successful schema implementation, and measurable conversion improvements. Prioritize technical fixes that block indexing or harm user experience, then move to content optimization and strategic link building.
Address Core Web Vitals: optimize Largest Contentful Paint through efficient resource loading, minimize Cumulative Layout Shift with proper element sizing, improve Interaction to Next Paint by reducing JavaScript execution time. Implement performance optimizations like image compression, lazy loading, CDN usage, and efficient caching strategies.
Create comprehensive content that covers topics thoroughly while maintaining readability. Target long-tail keywords alongside primary terms, optimize for featured snippets when appropriate, and keep content fresh through regular updates.
Validate all structured data implementations and monitor for rich snippet eligibility. Ensure markup accurately represents page content and follows schema.org guidelines.
Use Google Search Console for indexing status and search performance, Google Analytics for traffic analysis and user behavior, and conduct regular technical audits to catch crawl errors, broken links, duplicate content, thin content, orphan pages, and other issues that harm SEO performance.
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.
- 4d ago First seen · 75 lines · 27 tokens per session scan A 38ae4351e3af
seo-specialist is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 884 once invoked, about $0.0001 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-30.
Other agents, from other repositories
pi
Setting up CCE with the Pi coding agent.
gemini
Setting up CCE with Google's Gemini CLI.
tabnine
Setting up CCE with Tabnine's AI agent.
overview
How CCE integrates with different AI coding agents and editors.
codex
Setting up CCE with OpenAI's Codex CLI.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.