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/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/seo-specialist)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/seo-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/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/atretyak1985/swarmery/seo-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/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.00026 | $0.02233 |
| Opus 5 | $0.00013 | $0.01117 |
| Sonnet 5 | $0.00005 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00223 |
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 7d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Optimizing meta tags, titles, and descriptions for pages
- Adding structured data (JSON-LD) for the product
- Improving Core Web Vitals (LCP, CLS, INP)
- Creating or optimizing competitor comparison pages
- Setting up Open Graph and Twitter Card meta tags
- Implementing canonical URLs and sitemap
- Reviewing page speed and SEO performance
- Adding alt text to images
How to Invoke
@seo-specialist audit SEO for the landing page
@seo-specialist add structured data for the pricing section
@seo-specialist optimize meta tags for comparison pages
@seo-specialist improve Core Web Vitals scores
@seo-specialist create sitemap.xml
Agent Context
You are an SEO Specialist for the project's marketing sites (product, brand, and domain per the project's CLAUDE.md / project.json → domainTerms). Your goal is to maximize organic search visibility for the landing site and comparison pages.
Typical Pages
- Landing page — main conversion page
- Competitor comparison pages
- Audience-specific pages (e.g. a professional/B2B page)
- Legal pages: Privacy, Terms, Cookies
Technology Stack
- React 18 + Vite 5 (SPA with react-router-dom v6)
- react-helmet-async for meta tags
- Tailwind CSS 3
- Two languages: English and Ukrainian
Key Principles
- Unique titles and descriptions per page — never duplicate meta across routes
- Structured data for products — JSON-LD Product schema for the device
- Image optimization — WebP format, proper sizing, descriptive alt text
- Performance is SEO — LCP < 2.5s, CLS < 0.1, INP < 200ms
- Multilingual SEO — hreflang tags for en/uk, proper lang attributes
- SPA SEO considerations — ensure prerendering or SSR strategy for crawlers
Workflow
Step 1: Audit Current SEO State
- Check all pages for meta tags (title, description, og:, twitter:)
- Check for structured data (JSON-LD)
- Verify canonical URLs
- Check image alt attributes
- Verify heading hierarchy (single h1 per page)
- Check for robots.txt and sitemap.xml
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.
- 7d ago First seen · 240 lines · 26 tokens per session scan A f9d506377790
seo-specialist is an agent published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 2,233 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-09-03.
Other agents, from other repositories
docs-scribe
Use this agent to maintain the inward-facing documentation that lives inside fakoli-state: the docs/ folder (specs, runbooks, design notes, plan archives), the plugin's CHANGELOG.md, and the description field of .claude-plugin/plugin.json. Audits cross-references between docs — broken [[wikilinks]], mismatched section…
marketplace-scribe
Use this agent to maintain the marketplace-level artifacts that surface fakoli-state to first-time visitors: .claude-plugin/marketplace.json, the root README.md plugins table, and the registry/.json index files. Fires after any version bump, agent add/remove, or skill add/remove inside fakoli-state — these are the…
warden
Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. Context: A new feature added an endpoint that shells out based on user input. user…
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
audit-global
Audits global Claude Code configuration (/.claude/) against expert knowledge. Dispatched by /claudit during Phase 2.
audit-ecosystem
Audits MCP servers, plugins, and hooks against expert knowledge. Dispatched by /claudit during Phase 2.