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/huifer/claude-code-seo/seo-checkgit clone --depth 1 https://github.com/huifer/claude-code-seoWrote 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/huifer/claude-code-seo/seo-check)<a href="https://agentmods.dev/commands/huifer/claude-code-seo/seo-check"><img src="https://agentmods.dev/badge/commands/huifer/claude-code-seo/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 | $0.00011 | $0.01817 |
| Opus 5 | $0.00005 | $0.00908 |
| Sonnet 5 | $0.00002 | $0.00363 |
| Haiku 4.5 | $0.00001 | $0.00182 |
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.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
对当前工作目录或指定文件进行快速 SEO 检查，重点关注元数据完整性和明显的 SEO 问题。
功能
快速 SEO 检查适用于：
- 检查单个页面的 SEO 状况
- 快速识别明显的 SEO 问题
- 提供即时修复建议
- 无需完整审计即可获得快速反馈
参数
$1或$ARGUMENTS: 可选的文件或目录路径- 如果不提供，检查当前工作目录
- 可以是单个文件路径
- 可以是目录路径（检查目录下所有页面）
检查项目
元数据检查
- ✓ Title 标签存在性和长度
- ✓ Meta Description 存在性和长度
- ✓ Open Graph 标签完整性
- ✓ Twitter Cards 标签
- ✓ Canonical URL
- ✓ Viewport 配置
内容检查
- ✓ H1 标题（唯一性）
- ✓ 图片 alt 文本
- ✓ 链接锚文本
- ✓ 内容长度（初步判断）
技术检查
- ✓ robots.txt 文件存在性
- ✓ 页面加载速度提示
- ✓ 移动友好性提示
- ✓ HTTPS 配置
使用示例
示例 1：检查当前目录
/seo-check
输出：
🔍 快速 SEO 检查
📁 检查目录：app/
📄 发现文件：8 个
快速检查结果：
✅ 优秀（6/8）
- /, /about, /services, /blog, /contact, /team
⚠️ 需要关注（2/8）
1. /blog/[slug]
- ⚠️ Title: 65 字符（建议：50-60）
- ⚠️ 缺少 Twitter Cards
2. /products/[id]
- ❌ 缺少 Description
- ❌ 缺少 OG 标签
建议优先修复 /products/[id]，它缺少关键元数据。
需要详细分析吗？使用 /seo-audit 进行完整审计。
示例 2：检查单个文件
/seo-check app/about/page.tsx
输出：
🔍 快速 SEO 检查
📄 文件：app/about/page.tsx
元数据检查：
✅ Title: "关于我们 | YourBrand" (16 字符) ✓
✅ Description: "了解我们的团队、使命和价值观..." (85 字符) ✓
✅ OG 标签完整 ✓
❌ Twitter Cards 缺失 ⚠️
✅ Canonical URL ✓
内容检查：
✅ H1 标题唯一 ✓
⚠️ 2 个图片缺少 alt 文本
✅ 内容长度充足 (450 词) ✓
技术检查：
✅ robots.txt 存在 ✓
✅ HTTPS 配置 ✓
✅ Viewport 配置 ✓
总结：页面 SEO 状况良好，建议添加 Twitter Cards 标签并修复图片 alt 文本。
需要我生成修复代码吗？
示例 3：检查目录
/seo-check app/blog/
输出：
🔍 快速 SEO 检查
📁 检查目录：app/blog/
📄 发现文件：12 个
博客页面检查结果：
✅ 优秀（8/12）
所有元数据完整，结构化数据正确
⚠️ 需要改进（3/12）
1. /blog/post-1 - Title 过长（68 字符）
2. /blog/post-5 - Description 过短（50 字符）
3. /blog/post-9 - 缺少 OG 图片
❌ 严重问题（1/12）
1. /blog/post-12 - 完全缺少元数据
建议：
1. 立即修复 /blog/post-12（添加所有元数据）
2. 优化 Title 和 Description 长度
3. 为所有博客文章添加 OG 图片
需要我为这些页面生成优化的元数据吗？
输出格式
简洁模式（默认）
🔍 快速 SEO 检查
✅ 12 个文件已检查
⚠️ 4 个文件需要改进
❌ 1 个文件有严重问题
优先修复：
1. [文件路径] - [问题描述]
2. [文件路径] - [问题描述]
3. [文件路径] - [问题描述]
建议：[快速修复建议]
详细模式
当检测到问题时，自动提供详细的分析和修复建议。
检查标准
Title 检查
中文：
- ✓ 最佳：20-30 字符
- ⚠️ 可接受：15-40 字符
- ❌ 问题：< 15 或 > 40 字符
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 · 288 lines · 11 tokens per session scan A 778db8391fe7
seo-check is a command published in the GitHub repository huifer/claude-code-seo (110 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 1,817 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.