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 commands/mtvrkan/senior-dev-kit/seo-checkgit clone --depth 1 https://github.com/mtvrkan/senior-dev-kitWrote 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/commands/mtvrkan/senior-dev-kit/seo-check)<a href="https://agentmods.dev/commands/mtvrkan/senior-dev-kit/seo-check"><img src="https://agentmods.dev/badge/commands/mtvrkan/senior-dev-kit/seo-check.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.1 | $0.00019 | $0.00717 |
| Opus 5 | $0.00010 | $0.00358 |
| Sonnet 5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
seo-check 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 5d 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.
What it actually says
/seo-check
Audit the project for SEO, AEO (AI Engine Optimization), Core Web Vitals, and technical SEO issues: $ARGUMENTS
You are running an SEO and AEO audit. Analyze the codebase for SEO issues and optimization opportunities.
Full checklists, expected metadata shape, JSON-LD schema table, and CWV risk detail are in
agent_docs/seo-patterns.md — read it before auditing rather than re-deriving these from scratch.
Step 1 — Detect framework. Next.js (App Router vs Pages) / Nuxt / SvelteKit / Astro / Remix — each has a different metadata API; check agent_docs/seo-patterns.md for the framework-specific shape.
Step 2 — Metadata audit. Scan page/layout files against seo-patterns.md's metadata checklist (title/description length, canonical, OG tags, twitter:card, duplicate metadata across pages).
Step 3 — Structured data check. Look for JSON-LD in page files; flag missing/incorrect schema per seo-patterns.md's page-type → schema table, and syntax errors or missing required fields.
Step 4 — Technical SEO. sitemap/robots presence and correctness, 404 page, image alt coverage, JS-only internal links, unintended noindex, <h1> uniqueness and heading hierarchy, mobile viewport meta.
Step 5 — Core Web Vitals risk scan. LCP (hero image priority/fetchpriority, missing sizes), CLS (<img> missing dimensions, non-next/font Google Fonts link, post-hydration shift), INP (long handlers without startTransition/debouncing, heavy per-render useEffect).
Step 6 — AEO / AI Engine Optimization. Apply seo-patterns.md's AEO principles (direct-answer H1/lead paragraph, structured facts, definition pattern, cited sources, FAQ question-headings).
Output format:
SEO AUDIT REPORT
================
CRITICAL:
✗ Missing title on: [pages]
✗ Missing canonical on: [pages]
✗ [page] blocked by robots.txt / noindex
HIGH:
✗ Missing sitemap.ts / sitemap.xml
✗ [count] pages missing description
✗ [count] images without alt text
✗ Missing JSON-LD on: [page types]
MEDIUM:
⚠ LCP risk: [location] — hero image without priority
⚠ CLS risk: [location] — image without dimensions
⚠ Title too long: [page] — [current char count] chars
LOW / OPPORTUNITIES:
→ Add FAQPage schema to [page] (AEO improvement)
→ Add BreadcrumbList schema to [page]
→ First paragraph on [page] could be more direct answer
AEO SCORE: [Good / Needs work / Poor]
TECHNICAL SEO SCORE: [Good / Needs work / Poor]
CWV RISK: [Low / Medium / High]
TOP FIXES (prioritized by impact):
1. [most impactful]
2. [second]
3. [third]
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.
- 5d ago First seen · 62 lines · 19 tokens per session scan A 00f5297f4bbd
seo-check is a command published in the GitHub repository mtvrkan/senior-dev-kit (5 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 717 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.