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-auditgit 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-audit)<a href="https://agentmods.dev/commands/huifer/claude-code-seo/seo-audit"><img src="https://agentmods.dev/badge/commands/huifer/claude-code-seo/seo-audit.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.00009 | $0.02805 |
| Opus 5 | $0.00005 | $0.01403 |
| Sonnet 5 | $0.00002 | $0.00561 |
| Haiku 4.5 | $0.00001 | $0.00281 |
Grade A, and why
seo-audit 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
执行完整的 SEO 审计，扫描所有页面和组件，生成详细报告和 SEO 评分（0-100 分）。
功能
全面的 SEO 审计包括：
- ✅ 元数据优化分析
- ✅ 结构化数据检查
- ✅ 内容质量评估
- ✅ E-E-A-T 权威性审计 ⭐
- ✅ 内容策略分析 ⭐
- ✅ 技术 SEO 检查
- ✅ 100 分制评分系统（6 个维度）
- ✅ 优先级修复建议
参数
$1或$ARGUMENTS: 可选的项目目录路径- 如果不提供，检查当前工作目录
- 应该是 Next.js 项目的根目录
- 支持相对路径和绝对路径
使用示例
示例 1：审计当前目录
/seo-audit
输出：
🔍 开始全面 SEO 审计...
✓ 检测到项目类型：Next.js App Router
✓ 扫描目录：app/
✓ 发现页面：15 个
✓ 发现组件：23 个
✓ 分析配置文件
✓ 检测语言：中文（75%）
📊 正在计算 SEO 评分...
═════════════════════════════════════════════════════
SEO 审计报告
═════════════════════════════════════════════════════
📈 总体评分：78/100 ⭐⭐⭐⭐
评级：良好 - 你的网站 SEO 基础较好，但仍有改进空间
═════════════════════════════════════════════════════
📋 详细得分：
1️⃣ 元数据完整性：18/20 ✅
├─ Title: 7/8
│ ├─ ✓ 所有页面都有 Title
│ ├─ ⚠️ 3 个页面标题过长
│ └─ ⚠️ 2 个页面缺少目标关键词
├─ Description: 8/8 ✅
└─ OG & Twitter: 3/4
└─ ⚠️ 缺少 Twitter Cards
2️⃣ 结构化数据：12/15 ⚠️
├─ JSON-LD 存在: 7/7 ✅
├─ 必需字段: 3/4
│ └─ ⚠️ 部分页面缺少 datePublished
└─ 验证通过: 2/4
└─ ❌ 有警告需要修复
3️⃣ 内容质量：20/25 ⚠️
├─ 标题结构: 5/6
│ └─ ⚠️ 1 个页面有多个 H1
├─ 内容长度: 5/6 ✅
├─ 关键词使用: 3/4
├─ 链接质量: 4/4 ✅
├─ 多媒体: 1/3
│ └─ ❌ 缺少视频和图表
└─ Featured Snippets: 2/2 ✅
4️⃣ E-E-A-T 权威性：14/20 ⚠️
├─ 专业度展示: 4/7
│ ├─ ❌ 缺少具体案例研究 (1/3)
│ ├─ ✓ 技术准确性良好 (2/2)
│ └─ ⚠️ 作者信息不完整 (1/2)
├─ 权威性建立: 5/7
│ ├─ ⚠️ 外部引用不足 (2/3)
│ ├─ ✓ 内容独特 (2/2)
│ └─ ⚠️ 支柱页面需要完善 (1/2)
└─ 信任度建设: 5/6 ✅
├─ ✓ 更新频率良好
├─ ✓ 数据来源透明
└─ ⚠️ 缺少关于页面 (1/2)
5️⃣ 内容策略：6/10 ⚠️
├─ 集群结构: 2/4
│ └─ ❌ 内部链接不足
├─ 内容日历: 2/3 ✅
└─ 关键词蚕食: 2/3 ✅
6️⃣ 技术 SEO：8/10 ✅
├─ robots.txt: 3/3 ✅
├─ 图片优化: 2/3
│ └─ ⚠️ 部分图片缺少 alt
├─ URL 结构: 2/2 ✅
└─ 移动友好: 1/2
└─ ⚠️ 响应式问题
═════════════════════════════════════════════════════
🎯 优先修复建议（按影响排序）
🔴 高优先级（+3 分以上）
1. [E-E-A-T] 添加案例研究和实际经验展示 (+2 分)
→ 在博客文章中添加真实案例
→ 分享实践经验教训
2. [E-E-A-T] 完善作者信息和关于页面 (+2 分)
→ 创建详细的作者简介页面
→ 添加关于页面
3. [内容策略] 优化集群内容的内部链接结构 (+2 分)
→ 确保所有相关内容互相链接
🟡 中优先级（+1-2 分）
4. [内容质量] 添加图表和视频内容 (+2 分)
5. [元数据] 添加 Twitter Cards 标签 (+1 分)
6. [结构化数据] 修复 JSON-LD 验证警告 (+2 分)
🟢 低优先级（+1 分以下）
7. [技术 SEO] 为图片添加 alt 文本 (+1 分)
8. [技术 SEO] 修复移动端响应式问题 (+1 分)
═════════════════════════════════════════════════════
📈 改进路线图
第 1 周：权威性建设
[ ] 添加 3 个案例研究
[ ] 创建作者简介页面
[ ] 添加关于页面
第 2 周：内容优化
[ ] 优化内部链接结构
[ ] 添加图表和视频
第 3 周：技术完善
[ ] 添加 Twitter Cards
[ ] 修复结构化数据
预期提升：78 分 → 90+ 分
═════════════════════════════════════════════════════
💡 下一步建议
需要我为任何建议提供详细的实施指导吗？
使用以下命令获取更多帮助：
/ee-audit --detailed # 详细 E-E-A-T 分析
/content-strategy # 内容策略建议
/pillar-pages --analyze # 支柱页面分析
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 · 382 lines · 9 tokens per session scan A 23840af6c649
seo-audit is a command published in the GitHub repository huifer/claude-code-seo (110 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 2,805 once invoked, about $0.0000 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.